You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am searching for a model-driven UI and found Mission Kontrol. The docs state, that it integrates directly on persistence layer:
Once hosted in your local environment you connect it to your database(s) and it will partially self-configure based on the schema. ...
We currently support both PostgreSQL and MySQL databases. We have future plans to support other databases, such as MSSQL.
This is direct integration with persistence layer is a bit too low. And, Mission Kontrol also implements own access control.
Is it possible to integrate Mission Kontrol on top of an existing API, which provides metadata about structure of entities and available commands, by implementing some adapter? I.e.:
Missing Kontrol for UI layer:
custom adapter implementation transforming API's model metadata to Mission Kontrol definitions,
custom Application API:
provides model metadata and schema,
provides data query and command endpoints,
custom Application access control layer:
enforcing ABAC, ReBAC or else,
custom Application domain logic layer,
custom Application persistence Layer.
To be honest, I had already implemented such model-driven UI-only panel on my own. However, it's a bit of ugly piece of code, and not published. Also, it's hard-coded to support exactly one type of model schema metadata API - not supporting adapters for custom API. And, so I'm researching open-source solutions to not reinvent the wheel, if it's already invented / implemented.
The text was updated successfully, but these errors were encountered:
I am searching for a model-driven UI and found Mission Kontrol. The docs state, that it integrates directly on persistence layer:
This is direct integration with persistence layer is a bit too low. And, Mission Kontrol also implements own access control.
Is it possible to integrate Mission Kontrol on top of an existing API, which provides metadata about structure of entities and available commands, by implementing some adapter? I.e.:
To be honest, I had already implemented such model-driven UI-only panel on my own. However, it's a bit of ugly piece of code, and not published. Also, it's hard-coded to support exactly one type of model schema metadata API - not supporting adapters for custom API. And, so I'm researching open-source solutions to not reinvent the wheel, if it's already invented / implemented.
The text was updated successfully, but these errors were encountered: