This document discusses the concepts of cloud native and why it is important. It defines cloud native as utilizing containers, dynamic management of infrastructure and applications, and building applications as microservices. The document provides examples of companies like the Financial Times and Gigaset that improved reliability, deployment velocity, and efficiency by moving to a cloud native approach using containers and microservices. It also discusses how cloud native relates to existing DevOps practices and the history and evolution of concepts like containers, orchestration, and microservices.
19. Case study: Financial Times
https://container-solutions.com/study-tech-transformation-financial-times/
20. Case study: Financial Times
Before After Change
Rollback ratio 20% 0.1% 200x
Lead time
Deployment
frequency
https://container-solutions.com/study-tech-transformation-financial-times/
21. Case study: Financial Times
Before After Change
Rollback ratio 20% 0.1% 200x
Lead time 120 days 15 min 4000x
Deployment
frequency
https://container-solutions.com/study-tech-transformation-financial-times/
22. Case study: Financial Times
Before After Change
Rollback ratio 20% 0.1% 200x
Lead time 120 days 15 min 4000x
Deployment
frequency
12 /
year
2000 /
year
170x
https://container-solutions.com/study-tech-transformation-financial-times/
37. 12 Factor Apps
https://12factor.net/
# Factor
I Codebase One codebase in version control, many deploys
II Dependencies Explicitly declare and isolate dependencies
III Config Store configuration in the environment
IV Backing services Treat backing services as attached resources
V Build, release, run Strictly separate build and run stages
VI Processes One or more stateless processes
38. 12 Factor Apps
https://12factor.net/
# Factor
VII Port binding Export services via port binding
VIII Concurrency Scale out via the process model
IX Disposability Fast startup and graceful shutdown
X Dev/Prod parity Dev / stg / prod as similar as possible
XI Logs Treat logs as event streams
XII Admin Processes Admin tasks as one-off processes