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.

Adopting a PaaS Solution (Part 1) - Red Hat DevOps & Microservices Conference 2017

161 views

Published on

By Nuno Santos - Enterprise Solutions Manager @Xpand IT

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Adopting a PaaS Solution (Part 1) - Red Hat DevOps & Microservices Conference 2017

  1. 1. Nuno Santos & Mario Sánchez Adopting a PaaS Solution
  2. 2. Infrastructure Platform Application IaaS host PaaS build SaaS use On- Premises CLOUD COMPUTING
  3. 3. • Focus on application development/maintenance • Development cycle automation • Portability • Scalability and Resource optimization • Security Containers Microservices BENEFITS
  4. 4. Power of Containers
  5. 5. CLASSIC INFRASTRUCTURE • Huge costs • Wasted resources • Inefficient deploys • Difficult to scale and migrate • Vendor lock-inInfrastructure Operating System Bins/Libs Application
  6. 6. 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
  7. 7. 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
  8. 8. Microservices
  9. 9. • 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?
  10. 10. • 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
  11. 11. • Heterogeneous architecture • Poor standards • Harder dependency management • More difficult to trace DRAWBACKS
  12. 12. • Systems too complex to manage • Isolated processing (no sync) • Resource intensive • Unsteady/Unpredictable elasticity source: https://martinfowler.com/microservices/ WHEN TO ADOPT
  13. 13. Icons made by Freepik from www.flaticon.comislicensedbyCC 3.0 BY Thank You!

×