forked from deegree/deegree3
-
Notifications
You must be signed in to change notification settings - Fork 2
WorkspaceNG
tfr42 edited this page Feb 12, 2021
·
9 revisions
- Exchanging or adding resources such as a raster file shall not require a reload and the resource is immediately available (within milliseconds)
- simplify / strength of deployment so that 1 webapp (1 container) can server all services (>500 endpoints)
- scaling of the services per dataset
- Raster data can be provided via drop-in in an existing service (no configuration of Store and TileMatrixSet as e.g. with GeoTIFF.
- Structure of the configuration files
- Possibility to use a data source (e.g. FeatureStore) in several services
- REST interface for configuration
- be more explicit in the configuration, example would be concepts introduced by Cloud Foundry
- be more stateless by getting environment specific information from the environment and not from the deegree workspace (state is stored in local filesystem)
- be more micro by splitting deegree heavy weight deployment bundle into a more microservices like self-contained system using technologies like docker
- support for other formats like YAML, JSON or sources such as a REST-API or databases shall be supported.
From the requirements that result from the new OGC API Specs (RESTfull) such as OGC API - features, a fundamental renewal / extension of the deegree workspace concept is necessary. The deegree workspace currently has the following restrictions:
- A workspace reload takes a long time if there are many configuration files in the workspace (from 100 files the duration of a reload is several seconds)
- During the reload of resources, other resources (such as services) are not available
- the workspace concept is too deeply interwoven with the deegree core (refactoring required)
- 1 workspace is coupled with 1 webapp and therefore several webapps (50 MB) must be deployed if several workspace configurations are to be operated in parallel on one Tomcat instance.
- no configurations can be shared across multiple workspaces
Related issues: