The document discusses the evolution of application development from monolithic backends in the 1990s to modern cloud native applications (CNAs). CNAs are optimized for modern distributed systems, use containers, are dynamically managed, and use microservices. The Cloud Native Computing Foundation aims to drive adoption of this new paradigm. For CNAs to work at scale, they need to be orchestrated regarding locality, lifecycle, and elasticity. The document then explores options for orchestrating CNAs, including fully automated management, self-organizing components, and ephemeral event-triggered functions. It also discusses tradeoffs between centralization and self-organization.

1. Beyond 12 Factor -
Developing Cloud
Native Applications
OpenCloud Day 2016
June 16, 2016
Maximilian Schöfmann | @schoefmann
Container Solutions

4. The Mission
Mission of the Cloud Native Computing Foundation.
The Foundation’s mission is to create and drive the adoption of a new computing
paradigm that is optimized for modern distributed systems environments
capable of scaling to tens of thousands of self healing multi-tenant nodes. Cloud
native systems will have the following properties:
(a) Container packaged. Running applications and processes in software
containers as an isolated unit of application deployment, and as a mechanism to
achieve high levels of resource isolation. Improves overall developer experience,
fosters code and component reuse and simplify operations for cloud native
applications.
(b) Dynamically managed. Actively scheduled and actively managed by a central
orchestrating process. Radically improve machine efficiency and resource
utilization while reducing the cost associated with maintenance and operations.
(c) Micro-services oriented. Loosely coupled with dependencies explicitly
described (e.g. through service endpoints). Significantly increase the overall
agility and maintainability of applications.
The foundation will shape the evolution of the technology to advance the state of
the art for application management, and to make the technology ubiquitous and
easily available through reliable interfaces.

5. The Mission
Mission of the Cloud Native Computing Foundation.
The Foundation’s mission is to create and drive the adoption of a new computing
paradigm that is optimized for modern distributed systems environments
capable of scaling to tens of thousands of self healing multi-tenant nodes. Cloud
native systems will have the following properties:
(a) Container packaged. Running applications and processes in software
containers as an isolated unit of application deployment, and as a mechanism to
achieve high levels of resource isolation. Improves overall developer experience,
fosters code and component reuse and simplify operations for cloud native
applications.
(b) Dynamically managed. Actively scheduled and actively managed by a central
orchestrating process. Radically improve machine efficiency and resource
utilization while reducing the cost associated with maintenance and operations.
(c) Micro-services oriented. Loosely coupled with dependencies explicitly
described (e.g. through service endpoints). Significantly increase the overall
agility and maintainability of applications.
The foundation will shape the evolution of the technology to advance the state of
the art for application management, and to make the technology ubiquitous and
easily available through reliable interfaces.

6. www.container-solutions.com | info@container-solutions.com
Some History…
1990s
fat clients
monolithic backend on
heavyweight middleware
physical infrastructure,
bare metal servers

7. www.container-solutions.com | info@container-solutions.com
Some History…
1990s
fat clients
monolithic backend on
heavyweight middleware
physical infrastructure,
bare metal servers
2010-15
web/native apps
backends services +
managed cloud services
virtual machines,
public or private cloud

8. www.container-solutions.com | info@container-solutions.com
Some History…
1990s
fat clients
monolithic backend on
heavyweight middleware
physical infrastructure,
bare metal servers
2010-15
web/native apps
backends services +
managed cloud services
virtual machines,
public or private cloud
2015+
modular web apps
microservices
Multi-cloud,
containerisation

9. www.container-solutions.com | info@container-solutions.com
Moving Parts…
1990s 2010-15 2015+
fat clients web/native apps modular web apps
backends services +
managed cloud services
monolithic backend on
heavyweight middleware
microservices
physical infrastructure,
bare metal servers
virtual machines,
public or private cloud
Multi-cloud,
containerisation
10^1
handful of
servers
10^2
dozens-
hundreds
of VMs
10^3
thousands
of containers

10. 12 Factor12 Factor12 Factor

11. www.container-solutions.com | info@container-solutions.com

12. www.container-solutions.com | info@container-solutions.com
VI. Processes
Execute the app as one or more stateless processes
IX. Disposability
Maximize robustness with fast startup and graceful shutdown

13. www.container-solutions.com | info@container-solutions.com
“A microservice system is stateful, even if all
constituent services are stateless”
Lukasz Guminski on container-solutions.com/containerpilot-on-mantl

14. www.container-solutions.com | info@container-solutions.com
CNAs want to be orchestrated

15. www.container-solutions.com | info@container-solutions.com
CNAs want to be orchestrated
Locality: Where should I run?

16. www.container-solutions.com | info@container-solutions.com
CNAs want to be orchestrated
Locality: Where should I run?
Lifecycle: What should I do when I start, stop, crash?

17. www.container-solutions.com | info@container-solutions.com
CNAs want to be orchestrated
Locality: Where should I run?
Lifecycle: What should I do when I start, stop, crash?
Elasticity: What happens on load spikes or idling?

18. www.container-solutions.com | info@container-solutions.com
Schedulers, Resource Managers

19. www.container-solutions.com | info@container-solutions.com
Schedulers, Resource Managers
NOT ENOUGH!

20. Options

21. Options
fully automated
application mgm?

22. Options
self-organising
components?
fully automated
application mgm?

23. Options
self-organising
components?
ephemeral, event-
triggered functions?
fully automated
application mgm?

24. Lifetime of individual components
short lived
long lived

25. www.container-solutions.com | info@container-solutions.com
Smarts are in a central management software,
knows state of all components
Examples:
• Mesos Frameworks, e.g. for elasticsearch
• Vitess from YouTube (MySQL scaling)
fully automated
application mgm?

26. www.container-solutions.com | info@container-solutions.com

27. www.container-solutions.com | info@container-solutions.com
Minimesos.org
+ github.com/ContainerSolutions/mesos-starter (Spring Boot boiler plate)

28. www.container-solutions.com | info@container-solutions.com
Custom Kubernetes Schedulers
+ github.com/kelseyhightower/scheduler

29. www.container-solutions.com | info@container-solutions.com
Smarts are in individual components, aware of own
state and some important siblings
Examples:
• ContainerPilot (Joyent)
• Habitat (Chef)
• Ringpop (Uber)
self-organising
components?

32. www.container-solutions.com | info@container-solutions.com
ContainerPilot (Joyent)

33. www.container-solutions.com | info@container-solutions.com
autopilotpattern.io

34. www.container-solutions.com | info@container-solutions.com
Components react to events and rely on runtime, fully
unaware of their surroundings
Examples:
• AWS Lambda (Amazon)
• Cloud Functions (Google)
• Kubernetes Funktion (Fabric8)
ephemeral, event-
triggered functions?

35. www.container-solutions.com | info@container-solutions.com
serverlessconf.io
serverless.com
github.com/fabric8io/funktion
FaaS (“Function as a Service”)

36. www.container-solutions.com | info@container-solutions.com

37. www.container-solutions.com | info@container-solutions.com
TANSTAAFL

38. www.container-solutions.com | info@container-solutions.com
systemautonomy&resiliency
standardisation & abstraction
10^1 10^2 10^3 10^4 10^5 10^6 10^7
The power of abstraction

39. www.container-solutions.com | info@container-solutions.com
systemautonomy&resiliency
standardisation & abstraction
10^1 10^2 10^3 10^4 10^5 10^6 10^7
The power of abstraction

40. www.container-solutions.com | info@container-solutions.com
systemautonomy&resiliency
standardisation & abstraction
10^1 10^2 10^3 10^4 10^5 10^6 10^7
The power of abstraction

41. www.container-solutions.com | info@container-solutions.com
systemautonomy&resiliency
standardisation & abstraction
10^1 10^2 10^3 10^4 10^5 10^6 10^7
The power of abstraction

42. www.container-solutions.com | info@container-solutions.com
predictability&tunability
10^1 10^2 10^3 10^4 10^5 10^6 10^7
The price of scalability

43. www.container-solutions.com | info@container-solutions.com
predictability&tunability
whole system cognitive tax
10^1 10^2 10^3 10^4 10^5 10^6 10^7
The price of scalability

44. www.container-solutions.com | info@container-solutions.com
Central management vs. self-organisation
Central management: Higher-level functions
- Movement
- Reasoning
- …
Self-organisation: Lower-level functions
- Cell repair and growth
- Knee-jerk reactions
- …

45. maximilian.schoefmann@container-solutions.com | @schoefmann
container-solutions.com/careers
softwarecircus.io (Aug 31 - Sep 2)