Containerised Applications

• Supported by most FaaS, PaaS and all CaaS systems.
• Portability through images
• Integration of arbitrary executables, processes, protocols
• Isolation of long-runing processes

Source to Container

Division of hardware resources by implementing many instances with isolation properties.

Standard image spec: Open Container Initiative (OCI)

LXC

• Linux specific, vendor neutral
• boot from directory
• namespacing of system resources in the Linux kernel
• integrate with python lib

Rocket

• CoreOS / RedHat
• book from AppC or Docker container image
• namespacing of system resources as processes without daemon
• integrate with systemd

Docker

• Docker Inc
• boot from Docker container image
• interpretation from Dockerfile
• namespaceing of system resources as processes through central daemon
• integrate with composition and computing tools (k8)

Container Composition

Docker Compose

Describe with docker-compose.yml files

• set of docker containers
• build and run config
• dependencies

• instance details

  • replicas
  • restart policies
  • placement
  • networking
  • volumes

    version: '2.1'
    services:
      myservice:
        image: myimage
        restart: always
        depends_on:
          - myotherservice
        environment:
          - VAR=value
        ports:
          - "80:443"
        logging:
          options:
            max-size: "10m"

Compose tools for log merging and command execution per instance.

docker-compose up
docker-compose down --volumes

Container Ecosystem

Sites on which containerised service implementations are offered: Hubs, Stores, Exchanges, Marketplaces

    Containerised Application
    ├── Monolithic
    ├── Microservices
    │   ├── Master-Slave
    │   ├── Nested-Container

Related Processes Per Container (RPPC)

Container-Native Architecture

Containers in VMs - simple but limited, more complex, single point of failures

Cloud-native with data-center as a single Docker host, routing and discovery components