Cloud-Native Microservices
1 like•306 views
This document discusses moving from monolithic applications to cloud-native microservices across multiple clouds. It outlines issues with monoliths like lack of scalability and availability. Microservices address these by isolating contexts into fine-grained, independently deployable services. However, microservices introduce infrastructure complexity around provisioning, observability, and testing. The cloud-native approach advocates for building applications in a way that leverages cloud-native technologies. Multi-cloud strategies can provide portability, avoid vendor lock-in, increase resilience, and lower costs by running workloads across clouds.
Cloud-Native Microservices
- 1. From Monolith to Multi-Cloud Cloud-Native Microservices
- 2. @diego_pacheco ❏ Cat's Father ❏ Principal Software Architect ❏ Agile Coach ❏ SOA/Microservices Expert ❏ DevOps Practitioner ❏ Speaker ❏ Author diegopacheco http://diego-pacheco.blogspot.com.br/ https://goo.gl/eEqvzl About me...
- 3. Monolith Issues ❏ Hard to maintain ❏ Too much Coupling ❏ Low level of Isolation / Abstraction ❏ Bottleneck for Innovation ❏ It's not COST effective ❏ Availability Issues ❏ Scalability Issues ❏ Low Development Engagement Shared DB Monolith UI
- 4. Default Integration Approach Shared DB Monolith UI Monolith UI Monolith UI
- 5. How did we get here?
- 6. Architecture Matters! ❏ Only COST orientation is dangerous. ❏ How we do things Matters! ❏ We need to care how we do things. ❏ Branches are a smell of bad architecture. ❏ Mindset Shift: ❏ Cheap Vendors -> Skilled Developers ❏ Short Term -> Long Term ❏ Coupling -> Abstraction ❏ Process -> Automation
- 7. SOA / Microservices to Rescue ❏ Microservices are a flavor of SOA ❏ SOA X MSA ❏ Isolation ❏ Context Bounded / Fine-Grained services ❏ Require new tooling ❏ Require new testing
- 8. Infrastructure Complexity ❏ Provisioning ❏ Telemetry / Observability ❏ Testing? ❏ Chaos Testing? ❏ Canary? ❏ AB/Testing? ❏ Databases: COST VS Managed Services VS Flexibility ❏ Slower than microservices
- 10. CNCF
- 13. Why you should care? ❏ Digital Transformation Enabler ❏ Portability ❏ Avoid Vendor Lock In ❏ Run Multi-Cloud: Be more Resilient, benefit from lower cost ❏ Remove Devops Engineering Complexity(Plumbing)
- 14. From Monolith to Multi-Cloud Cloud-Native Microservices