Monoliths vs microservices
- 1. page 1 Arabic DevOps Ahmad Ezzeir
- 2. page 2 Agenda • Definitions (Monolithic, Microservices) • Benefits • Challenges • When to use • My advice
- 3. page Definition • Applications Architecture • Single codebase • Single process • Single host • Single database • consistent technology Monolith
- 4. page Benefits • Simplicity • One codebase Easy to find things • Deployment one application to replace • Simple testing Monolith
- 5. page Challenges • Deployments • everything must be deployed together • Risky • required downtime • Scale (Horizontal vs vertical) • Horizontal scaling often not possible (whole application must be scaled) • vertical expensive • could becomes legacy technology Monolith
- 6. page when to use • Small Teams • You’re Building An Unproven Product or Proof of Concept. (check the business value) • You Have No Microservices Experience • Not mature DevOps Environment Monolith
- 7. page Definition • Componentization via service • Decentralization data management • mixed technologies Microservice
- 8. page Benefits • Small Services: • Easier to understand • Technology Choice • Adopt new technology • Individual Deployment • Lower risk • Minimize downtime • Frequent updates • Scaling • Scale services individually Microservice
- 9. page Challenges • Developer Productivity • Complex Interactions • Deployment “DevOps Experience” • Monitoring • Mature DevOps Environment • Containers and Containers orchestration Experience • Learning curve Microservice
- 10. page When to use • Product • business value • Very Mature DevOps Environment with many DevOps Engineers. • NOT Recommending to start any project with Microservices software architecture • examples: Amazon.com, Uber, Netflix , ebay Microservice
- 11. page 11 • My Advice •learn microservice
- 12. Thank You