Tale of Two Workloads And One Cloud
1 like919 views
The document discusses the transition from legacy infrastructures to cloud-native architectures, highlighting the differences in design principles and workload management. It emphasizes the need for resilient, distributed systems that can handle rapid scaling and failures, and advocates for treating cloud instances as disposable commodities rather than unique pets. The authors also touch upon the co-existence of legacy applications and cloud-native designs within unified cloud environments.
Tale of Two Workloads And One Cloud
- 1. Tale Of Two Workloads And One Cloud: Aaron Delp Cloud Architect SolidFire @aarondelp From Legacy to Cloud Native Kenneth Hui Technology Evangelist Rackspace @hui_kenneth
- 2. Kenneth Hui @hui_kenneth Technology Evangelist Rackspace OpenStack Ambassador Who Are We? Aaron Delp @aarondelp Cloud Architect SolidFire Cisco Champion
- 3. 3 Tale of Two Workloads
- 4. Legacy Design Principles Monolithic Architecture Steady State Workloads Operator Focused
- 5. Design Goal: Resilient Infrastructures
- 6. Legacy Infrastructure Consumption Models 6 On-Prem Infrastructure Managed Hosting
- 7. Cloud Native Design Principles Distributed Architecture Spikey Worloads Developer Focused
- 8. Design Assumption: Fragile Infrastructures
- 9. What’s Wrong with the Cloud? 9
- 10. We Architect Cloud Native for Rapid Scale 10
- 11. At Scale Chaos and Failures Are Inevitable 11
- 12. So Design for Failure 12
- 13. Let the Application Handle It’s Own Resiliency 13
- 14. 14 Choose Cattle Over Pets • Pets needs care and feeding – Name the VM – Tune and groom regularly – Feed pets with good food and supplements – Take pets to the vet when they are sick • Cattle are disposable – Cloud instances are not unique – Tune and groom apps not the cattle – Replace when necessary – Shoot the cattle when it is sick
- 15. Focus on Scaling Horizontally 15
- 17. For Example: Think CAP Theorem 17
- 18. Cloud Consumption Models 18 Public Cloud Private Cloud
- 19. 19 What About Those Pesky Legacy Apps?
- 20. Design Architecture For the Workload 20 Legacy Applications Development Labs & Test Environments Mobile Applications High Performance Computing Batch processing Web Applications Disaster Recovery
- 22. 22 One Cloud: Multi-hypervisor OpenStack
- 23. 23 One Cloud: Multi-hypervisor CloudStack
- 24. 24 CloudStack: Designing for Legacy Apps
- 25. 25 CloudStack: Designing for Cloud Native Apps
- 26. 26 Let’s Stay In Touch
- 27. For More Information Kenneth Hui @hui_kenneth ken.hui@rackspace.com http://cloudarchitectmusings.com http://www.rackspace.com./blog/author/ kenneth-hui Aaron Delp @aarondelp Aaron.delp@solidfire.com The Cloudcast Podcast www.aarondelp.com
- 28. 28