d.velop AG pursues a cloud-first strategy in development. New apps or updates in the cloud therefore have priority. However, the development of on-premises systems is not neglected.
The cloud-first strategy allows us to make changes and new apps available quickly in the cloud. These changes or innovations are often also adopted in on-premises systems, as the architecture is almost identical.
Some apps are currently only available for one of the two operating modes. Other apps can be run in the other operating mode via a hybrid connection. The following table shows the main differences between the operating modes:
On-premises | Cloud | Hybrid | |
|---|---|---|---|
Registration of the apps | HTTP-Gateway | Approuter | HTTP-Gateway and Approuter If an app is available in both operating modes: Use the enableForceLocalAppMode parameter to specify the operating mode. |
Technical registration | Option 1 Manual registration via the configuration of HTTP-Gateway (http://localhost:4280/httpgateway/ui/) Option 2 Automatic self-registration of an app | For administrators Set up a new app via https://my.d-velop.cloud For developers Transmission of the provider name to d.velop and manual setup of the app in the provider configuration | Not available |
Installing the app | Manual configuration or via the vendor's setup program | Option 1 Booking via the d.velop store (http://store.d-velop.de) Option 2 Booking released apps or available apps from the provider via the cloud administration (https://my.d-velop.cloud) | Not available |
Header information | x-dv-tenant-id always corresponds to 0. x-dv-sig is not used. | x-dv-tenant-id corresponds to the tenant ID for distinguishing calls by tenants. x-dv-sig contains the signature of the registered app. | Not available |
Characteristics of the DMS configuration | The DMS is configured via the client component d.3 admin. No configuration possible via Rest API. | The DMS is configured via the configuration of the DMSConfig app using the Rest API. Configuration also possible via scripts and third-party components. | Use the enableForceLocalAppMode parameter to specify whether the local DMS app or the cloud app is to be used in hybrid mode. Then configure via d.3 admin (on-premises) or DMSConfig app (cloud). |
You can find information on the cloud basics at: https://help.d-velop.de/dev/getting-started-basics