Rich Container (Erl, Naserpour)
How can multiple containers be deployed so that they share the same namespace and IP address?
A regular container provides essential but very basic functions. Specifically, it supports commands to be stopped, started, paused and resumed. Applications and services hosted in containers can require many more features, making the usage of regular containers insufficient.
The application or service is deployed in a container with a wide range of enhanced features and functionality.
An advanced container engine is used to enable containers to deliver a number of commonly required features, such as health status monitoring, threads, stack, lock contention, network message statistics and conﬁguration information.
Burst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Cloud Authentication, Cloud Balancing, Elastic Environment, Infrastructure-as-a-Service (IaaS), Isolated Trust Boundary, Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Resource Workload Management, Secure Burst Out to Private Cloud/Public Cloud, Software-as-a-Service (SaaS)
Cloud Service A is deployed inside a rich container that provides extra features and can provide additional information about the cloud service.