Running Stateful Applications on Azure Container Instances

Presented at Microsoft Global Azure Bootcamp (Istanbul). It's about container architecture and Azure solutions to manage the state of containerized applications.

1. Running Stateful Applications on AZURE CONTAINER INSTANCES
2. SELÇUK USTA Software Development Manager @ /in/selcukusta selcukusta.com selcukusta ustasoglu selcukusta (at)gmail.com
3. Containers are not "lite" applications Don’t need to limit any functions of your applications.
4. Containers are not "not" hackable Containers share the kernel, other components of the host operating system. If there’s any vulnerability in the kernel, could affect your container.
5. Containers are not flea market "Single-process-per-container" is recommended design pattern for containerized applications.
6. Containers are not resource independent Resource management is so important in container orchestration. Because more than one container can be run on one host machine.
7. Containers are not Docker Docker is most popular containerisation platform, but there many other solutions out there; RKT, ContainerD, LXC, etc…
8. Containers are not virtual machines Containers are virtualizing the underlying operating system while virtual machines are virtualizing the underlying hardware (hardware-level-virtualization).
9. Containers are "os-level-virtualization" Kernel allows multiple isolated user-space instances for running processes.
10. Kernel Space RAM DISK (1) Read a file (IO Operation) (2) Memory allocation User Space Container Process(1) SYSTEM CALLS(2)
12. WHATS the DIFF? Share kernel Takes seconds to provision one Use host operation system Resource sharing Process-level isolation, less secure Have own kernel Takes minutes to provision one Have own operating system Resource allocation Fully isolated, hence more secure VIRTUAL MACHINES CONTAINERS
13. Can application be stateless?
14. All applications have state, but an application component can be stateless if it cleanly separates behaviors from data, and can fetch data required to perform any behavior. Jim Bugwadia
15. Application Data&IO Operations Session Connection Configuration Cluster
16. Data&IO Operations HOST Container HOST Container HOST Container Networked Volume
17. Application-2 Application-1 Application-3 Connection strings SSH Keys Application keys Configurations
18. App-Instance-2 App-Instance-1 App-Instance-3 Sessions
19. Connection WebSocket Server Handshake (HTTP Upgrade) Connection opened Bi-directional messages (open & persistent connection) One sides closes channel (connection closed)
20. Cluster App-Instance-2 App-Instance-1 App-Instance-3
21. State Solutions SQL Database Azure Redis Azure Traffic Manager Azure Load Balancer Azure Managed Disks Azure Key Vault
22. Azure Container Instances Run containerized applications without any concerns about infrastructure management
24. /in/selcukusta selcukusta.com selcukusta ustasoglu selcukusta (at)gmail.com Thank you…