This document discusses why cloud native computing matters and provides three case studies. It begins by explaining how infrastructure is changing with the rise of containerization solutions in the 2010s. It then discusses why people use cloud native technologies because they work well and have a great community behind them. Three case studies are presented where companies moved workloads to cloud native solutions on Kubernetes to increase agility, reduce costs, and improve developer productivity. The document concludes by noting that while technology challenges can be solved, changing organizational culture can be the hardest challenge to address.

1. TM
Why cloud native matters
16 January 2020
Cheryl Hung, Director of Ecosystem, CNCF
chung@linuxfoundation.org

2. 2
1. How infrastructure is changing
2. Why cloud native and case studies
3. What are the top challenges?
Agenda

3. 3
About me

4. How infrastructure is changing

5. 5

6. 6
Applications need to be agile, scalable, secure

7. 7
• Alibaba Sigma
• Amazon Apollo
• Apache Mesos
• Baidu Matrix
• Cloud Foundry Garden and
Diego
• CoreOS Fleet
• Docker Swarm
• Facebook Tupperware
• Google Borg and Omega
• Hashicorp Nomad
2010s (ish) solutions
• IBM Platform Symphony
• Joyent Triton
• Lyft v3 Infra
• Microsoft Service Fabric
• Netflix Titus
• Rancher Cattle
• Red Hat OpenShift v2 Broker
• Spotify Helios
• Tencent Gaia
• Twitter Aurora
• Uber Peleton

8. 8
Cloud Native Computing Foundation

9. Platinum members:
Incubating
Service
Mesh
Storage
Service
Discovery
Graduated
Package
Management
Distributed
Tracing API
Messaging
Distributed
Tracing
Software
Update Spec
SecurityNetworking
API
Orchestration Network ProxyMonitoring
Registry Key/Value
Store
Policy Container
Runtime
Container
Runtime
Logging
Remote
Procedure Call
Key/Value
Store
Storage Serverless Container
Security
Cloud Native Computing Foundation

10. Why cloud native and case studies

12. Why people really use cloud native:
It works
Great community

13. 13
It works

14. 14
Great
community

15. 15
Caveat

16. 16
Neutral home

18. 18
• Goal was to unify infrastructure and increase
velocity
• VMs + Puppet on bare metal
⇒ Docker containers + CoreOS Fleet +
OpenStack
⇒ Kubernetes on private cloud
• Went from 2 deployments per week to dozens
• Same applications run on 15-25% less
hardware resources
Case study 1

19. 19
• Goal was to scale securely
• EngineYard + Amazon Elastic Beanstalk
⇒ Kubernetes on AWS EC2 Spot
• Kubernetes clusters run at 1/10th the previous
cost
• Use Notary as a trust system to prove that
unknown code can’t be deployed in production.
Case study 2

20. 20
Case study 3 • Goal was to ship a modern customer
experience
• Private data centres and in-house infra
⇒ Docker containers on AWS
⇒ Kubernetes on AWS
• Went from 24 deployments to 500+ per year
• Could support both modern cloud native
applications and legacy Windows / .NET

21. What are the top challenges?

22. 22
CNCF Survey (~1000 respondents)

23. 23
Diversity and inclusion

24. 24
Contributions Rank
Red Hat 502688 2
Digital Ocean 3357 76
Rackspace ? ?

25. 25
Contributions Rank
Red Hat 502688 2
Digital Ocean 3357 76
Rackspace 2002 106

26. 26
Takeaways • Users expect continual innovation and
perfect performance.
• People use cloud native because 1) it works
2) a great community
• The hardest thing to change is culture.

27. 1st Wed of each month in Holborn

28. 28

29. Thank you
Slides at oicheryl.com