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.

The Journey to Becoming Cloud Native – A Three Step Path to Modernizing Applications

502 views

Published on

SpringOne Platform 2016
Speaker: Alois Reitbauer; Chief Technology Strategist, Dynatrace

The cloud has transformed the way we build applications. Early adopters prove that the benefits manifest in delivering value faster to the customer, less operational costs and more productive teams. The interesting question is how to get there, especially if you cannot simply start over and get your current applications benched. Through numerous customer engagements we have learned that there is a pattern followed by companies that do this successfully. This talk show you:

-How to deploy faster without breaking things
-Start decoupling a monolith without breaking your business logic.
-Help developers build application using a new paradigm
-Dynamically scale your applications to save costs
-Manage highly dynamic larger-scale micro services without increasing operational costs

As we will walk through the journey we share learning covering challenges and possible solutions on the organizational, development and operational side. As a company that has gone through this transformation itself while onboarding over 500 new customers we have some interesting stories to share.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

The Journey to Becoming Cloud Native – A Three Step Path to Modernizing Applications

  1. 1. Journey to Cloud Native How to move to the cloud in three steps • Alois Reitbauer, @aloisreitbauer
  2. 2. about:me Alois Reitbauer Chief Strategist Lead Innovation Lab (never smiles on photos)
  3. 3. Bimodal IT Not every project is a cloud project, but cloud thinking is everywhere
  4. 4. Develop Big monolithic application. Small interconnected purpose-built services.
  5. 5. Pizza Box Teams Small teams can deliver features into production
  6. 6. New Rules in the Game You build it, you run it. Werner Vogels, CTO Amazon
  7. 7. Ship Deploy Big Bang Releases of single special built applications. Small continuous service delivery of standardized delivery blocks.
  8. 8. Compute Hardwired datacenters. Datacenter as an API.
  9. 9. The journey to become cloud-native We see three different stages how companies embrace transformation
  10. 10. Stage 1: Continuous Delivery “Lift and Shift” to modern platforms Applications stay the same Release speed massively increases
  11. 11. Writing fast cloud native applications easy Rule #1: Don’t write slow code
  12. 12. Control code complexity N+1 interaction patterns - control flow design Duplicate interactions - bounded context, SPOF More than 10 service hops - hard to debug Highly asynchronous - hard to understand Unusual Log Activity
  13. 13. Continuous Performance Management
  14. 14. Stage 2: Refactoring towards Micro Services First micro services Scheduling and Orchestration Architectures become polyglot Independent Release Cycles
  15. 15. Writing fast cloud native applications easy Rule #1: Don’t write slow code Rule #2: Don’t write code that doesn’t scale
  16. 16. Control Environment Complexity Service Call Payload - < 500 kb Chatty services - > 50 service calls Inter-tier heavy interactions - granularity and locality Status Codes - only Ok is 200
  17. 17. Understand Micro Service Interactions
  18. 18. Stage 3: Dynamic Micro Services Up and down scaling near real time Advanced resilience mechanisms Infrastructure totally abstracted
  19. 19. Writing fast cloud native applications easy Rule #1: Don’t write slow code Rule #2: Don’t write code that doesn’t scale Rule #3: Understand application behavior
  20. 20. Watch your application live Health monitoring – symptoms Orchestration monitoring - causality Application monitoring - root cause
  21. 21. 7:00 a.m. Low Load and Service running on minimum redudancy 12:00 p.m. Scaled up service during peak load with failover of problematic node 7:00 p.m. Scaled down again to lower load and move to different geo location Deployments are no longer static
  22. 22. You don’t fly by hand here 820 Billion dependencies Network Problem Mushroom cloud effect
  23. 23. Container Network Monitoring
  24. 24. Make it part of your environment
  25. 25. Thank you! Alois Reitbauer alois.reitbauer@dynatrace.com @aloisreitbauer

×