Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Building Cloud Native Applications

Building Cloud Native Applications

  • Login to see the comments

  • Be the first to like this

Building Cloud Native Applications

  1. 1. Arun Gupta, @arungupta Principal Open Source Technologist, Amazon
  2. 2. @vivekpandey @jstrachan @pelegri @plmuir @singh_harpreet Kristin Nazrul
  3. 3. Key Primitives of a Cloud Native “…application is container-based” “…dynamically managed…” “…microservice oriented…” Application?
  4. 4. Containers Cloud Culture Technology Process People
  5. 5. 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
  6. 6. Containers must be first class citizens
  7. 7. Simple, easy to use, powerful consumption model Resource based pricing Fargate No instances to manage Container native API
  8. 8. Cloud Native Principle #1 Cloud Native Applications enable organizations to build and ship features faster without worrying about the collateral damage of failure/iteration.
  9. 9. CultureCloudContainers
  10. 10. Cloud Native Architecture Principles
  11. 11. 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
  12. 12. 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.
  13. 13. File tickets and wait for every step Self service, on-demand, no delays ! VS !
  14. 14. 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
  15. 15. 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.
  16. 16. Blast Radius Loosely Coupled Geographically Distributed Resiliency
  17. 17. 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.
  18. 18. Cloud Native Principle #4 Microservices reduce blast radius, can improve MTTR, and support globally distributed deployment models.
  19. 19. “You don’t add innovation to a culture, you get out of its way.” —Adrian Cockcroft, VP Cloud Architecture Strategy, AWS
  20. 20. INFRASTRUCTURE OPERATOR PLATFORM ARCHITECT
  21. 21. Enable Focus on Applications
  22. 22. Containers Cloud Culture

×