Provide a consistent back or mid-tier data service.
This library can run in any of three types of configurations:
- Configuration Driven
- Managed via Backplane Endpoints
- Hybrid (configuration plus endpoint)
The service looks for a Retold
stanza in the configuration. For instance:
{
...
"Retold": {
"MeadowModel": "./meadow-schema-extended.json"
},
...
}
The three auto-configured parameters are:
MeadowModel
MeadowEntitySchema
StrictureDDL
The service tries to do the right thing with strings versus arrays -- you can pass an array of models or a single. Likewise, you can pass an array of schemas or a single. It also supports grabbing all files of a single folder with the /*
suffix, and recursive with the /**
suffix. When used in this fashion, only .json
files are loaded from the folder(s).
POST /BackPlane/${VERSION}/Load/MeadowModel
This endpoint accepts a JSON blob of an entire Meadow model. It loads the entire model as a set of endpoints, and connects each endpoint to the default provider.
POST /BackPlane/${VERSION}/Load/MeadowSchema
This endpoint accepts a JSON blob of an entire Meadow model. It loads the entire model as a set of endpoints, and connects each endpoint to the default provider.
POST /BackPlane/${VERSION}/Load/StrictureDDL
This endpoint loads a Stricture DDL, compiles it into the composite Entity schemas and loads them as endpoints.
GET /BackPlane/${VERSION}/Model/Primary/
GET /BackPlane/${VERSION}/Model/Composite/
POST /BackPlane/${VERSION}/Settings
GET /BackPlane/${VERSION}/SetProvider/:ProviderName
GET /BackPlane/${VERSION}/SetProvider/:ProviderName/:Entity