Digital Distributed Containers (DDC)
| A Digital Distributed Container subscription is required. |
The Digital Distributed Container functionality allows to create stand alone container containing either a single or multiple services. Those containers can then be deployed on a container-based infrastructure and scaled according to the organization needs.
Single Service Container |
Micro-service pattern: An individual service is exported as a container that can be deployed on your organization’s infrastructure. |
Multi Service Container |
Bundled-service pattern: Multiple services are selected and exported as a container that can be deployed on your organization’s infrastructure. |
Each container requires its own license token to execute. A token of the proper type is required for each deployment. A deployment is defined as a container image being deployed in a single location. This means that locally scaling of a given container in the same location can be done with a single token, but geographical scaling requires a token per location.
Creating a Digital Distributed Container
In order to be able to build containers, the administrator must configure the base image for the containers.
Single Service Container
Single service containers are automatically created when a service is published to the Service Library from the modelers.
Each execution environment can be configured to build the containers either locally or push them to a remote registry.
Multi Service Container
Multi service containers are built on demand from the Service Library by selecting the services to include in the container and pushing the container image to a remote registry.