The key principles of cloud native applications are: 1. They enable organizations to build and ship features faster without worrying about failure or iteration. 2. They pay for what is used last month, not what may be needed next year, allowing teams to experiment and fail fast without significant investment. 3. They are self-service, API-driven, and automated, moving from requesting tickets for each step to self-service tools that empower teams.

1. Arun Gupta, @arungupta
Principal Open Source Technologist, Amazon

3. @vivekpandey @jstrachan @pelegri
@plmuir @singh_harpreet
Kristin
Nazrul

5. Key Primitives
of a Cloud Native
“…application is container-based”
“…dynamically managed…”
“…microservice oriented…”
Application?

6. Containers Cloud Culture
Technology Process People

7. The fast
companies are 2555x
faster than
the slow
Compared to low performers, high performers have:
46x more frequent code deployments
2555x faster lead time from commit to deploy
2604x faster mean time to recover from downtime
7.0x lower change failure rate
DevOps - Time to Value

8. Containers must be first class citizens

9. Simple,
easy to use,
powerful
consumption
model
Resource
based pricing
Fargate
No instances
to manage
Container
native API

10. Cloud Native Principle #1
Cloud Native Applications
enable organizations to build
and ship features faster without
worrying about the collateral
damage of failure/iteration.

11. CultureCloudContainers

12. Cloud Native Architecture Principles

13. Cloud Migration
Pay as you go
DATACENTER
Applications and data
Pay up front and
depreciate over
three years
Pay a month later
for the number of
seconds used

14. Cloud Native Principle #2
Pay for what you used last month,
not what you guess you will
need next year.
Enable teams to experiment, and
fail fast, without significant
investment.

15. File tickets and
wait for every step
Self service,
on-demand, no delays
!
VS
!

16. File tickets and
wait for every step
Self service,
on-demand, no delays
!
VS
!!
Deploy by filing a
ticket and waiting
days or weeks
Deploy by making an
API call self service
within minutes

18. Cloud Native Principle #3
Self service, API driven, automated.
Move from request tickets at every
step to self-service APIs and tools that
empower teams.

19. Blast
Radius
Loosely
Coupled
Geographically
Distributed
Resiliency

20. Microservices limit “blast
radius” for software incidents
Build and deploy loosely coupled
services.
Enable teams to move fast independently.
Reduce blast radius via service and
deployment isolation.

21. Cloud Native Principle #4
Microservices reduce blast radius, can
improve MTTR, and support globally
distributed deployment models.

22. “You don’t add innovation to a
culture, you get out of its way.”
—Adrian Cockcroft, VP Cloud Architecture Strategy, AWS

23. INFRASTRUCTURE
OPERATOR
PLATFORM
ARCHITECT

24. Enable Focus on Applications

25. Containers Cloud Culture