Adopting a PaaS Solution (Part 1) - Red Hat DevOps & Microservices Conference 2017
0 likes247 views
This document discusses adopting a Platform as a Service (PaaS) solution and the benefits of containers and microservices architectures. It outlines how PaaS focuses on application development and maintenance with automated development cycles, portability, scalability, and optimized resource usage. Containers provide benefits over virtualization like lighter weight with no need for a guest OS, improved scalability and performance. Microservices allow for scalable and flexible applications by decomposing them into independently deployable services.
Adopting a PaaS Solution (Part 1) - Red Hat DevOps & Microservices Conference 2017
- 2. Nuno Santos & Mario Sánchez Adopting a PaaS Solution
- 4. • Focus on application development/maintenance • Development cycle automation • Portability • Scalability and Resource optimization • Security Containers Microservices BENEFITS
- 6. CLASSIC INFRASTRUCTURE • Huge costs • Wasted resources • Inefficient deploys • Difficult to scale and migrate • Vendor lock-inInfrastructure Operating System Bins/Libs Application
- 7. VIRTUALIZATION • Better resource usage • Easier to scale Host Operating System Hypervisor Infrastructure VM Guest OS Application Bins/Libs VM Guest OS Application Bins/Libs • Requires Guest OS • Big footprint • Limited portability
- 8. CONTAINERIZATION Host Operating System Infrastructure Container Application Bins/Libs Container Application Bins/Libs Container Engine • Does not require Guest OS • Lightweight • Less CPU, RAM, storage • Improved scalability and performance • Greater portability
- 10. • Emerged from companies like Amazon, Facebook, Google, … • Scalable applications with minimized impacts of change • Features • Fine-grained • Flexible/Decentralized • Technology-agnostic • Independently deployed WHAT IS MICROSERVICES?
- 11. • Contrast with typical Monolithic applications • Decoupled functionality • Agility and flexibility • Low risk of change impacts • Ownership management • DevOps promotes microservices-based architectures • Quick to provision and deploy • Easy to scale and manage • Self-service approach smart endpoints, dumb pipes MICROSERVICES & DEVOPS
- 12. • Heterogeneous architecture • Poor standards • Harder dependency management • More difficult to trace DRAWBACKS
- 13. • Systems too complex to manage • Isolated processing (no sync) • Resource intensive • Unsteady/Unpredictable elasticity source: https://martinfowler.com/microservices/ WHEN TO ADOPT
- 14. Icons made by Freepik from www.flaticon.comislicensedbyCC 3.0 BY Thank You!