Container technologies for cloud-native apps

Architecting a container-based height for craving applications requires a holistic perspective of several capabilities and how they fit together. Regardless of either craving app professionals use a container-native or integrated-platform pattern, they contingency still select components and arrange them seamlessly. The anxiety design of container-based concentration platforms can be tangible as consisting of 8 layers, any with specific componentised technical capabilities.

Many open source options for a container-native settlement routinely concentration on one capability member (or a few) for assembly, while options for integrated patterns customarily hide a enclosure engine, enclosure orchestration, outmost formation and operations government layers together.

The initial covering is a enclosure engine, that provides a foundational execution environment. This sourroundings should support predefined pattern record formats of mainstream enclosure images, such as those from Docker, App Container and a Open Container Initiative. The sourroundings should not usually support enclosure runtimes, such as runC, Docker containerd, rkt, and cri-o, though also runtimes of VMs, such as runV, Clear Containers and LXD.17. It should afterwards be means to govern a set of customary build-ship-run operations for enclosure images and instances. These can operation from building an picture from pattern files to tagging an picture in a repository.