Cloud native principles
3 likesâ˘2,207 views
This document discusses cloud native principles and definitions. It covers the issues with bare metal servers, how virtualization was an improvement, and defines cloud native principles like using containers for isolation and portability, microservices, elasticity, and automation. It provides Pivotal's definition of cloud native including practices like DevOps, continuous delivery, and BOSH for consistent provisioning. While containers are common, cloud native does not require them - examples like NetflixOSS are given. Migrating applications to the cloud "as-is" can miss benefits, and principles like those defined can "raise the bar" of cloud applications.
Cloud native principles
- 2. @diego_pacheco â Cat's Father â Principal Software Architect â Agile Coach â SOA Expert â DevOps Practitioner â Speaker â Author diegopacheco http://diego-pacheco.blogspot.com.br/ https://goo.gl/eEqvzl About me...
- 3. Bare Metal â There are some issues: â Hardware Failures â Up-to-front-cost â Often is hard to get hardware due corp policies â Often people don't do hardware upgrades as much frequent â Can get very complex deal with directly hw/sw â Virtualization was one of the first steps towards improvement â Software was created and design consider hw/sw reality â Bare Metal and Cloud are different worlds â You can port some App to the Cloud "As-IS"
- 4. 12 Factor App - Back to the PaaS time
- 5. Cloud Native â Containers: Isolation and Portability â Dynamic Orchestrated (resources optimization) â OSS First â Microservices Oriented â Microservices requires some other concerns like: â Automation â Registry/Discovery â Distributed Tracking / Observability â Anti-Fragility / Chaos Engineering â Cloud Gives you: â Elasticity(Auto-Scaling) â On-Demand model https://www.cncf.io/
- 6. Cloud Native -- Pivotal definition â DevOps â Process â Tools â Culture â Continuous Delivery â Automation â Microservices â Automation â Registry/Discovery â Distributed Tracking / Observability â Anti-Fragility / Chaos Engineering
- 7. Cloud Native -- Pivotal definition â BOSH â Multi-Cloud Support (avoid Lock-in) â Clean Separation of Systems â Consistent-rapid provisioning â Scale Up/Down â Built in Health monitoring â Faul Remediation â Canary Deployments
- 8. Cloud Native == Containers? â Containers are great but... â Besides what CNCF says: â You can still be Cloud Native and don't use containers. â i.e: NetflixOSS Stack â Big Cloud Vendors like: Amazon, Google and Microsoft: â Provide: IaaS, PaaS, CaaS â There are more than one way to have portability besides docker, like: â Spinnaker â Mesos
- 9. NetflixOSS
- 10. Architecture considerations Design Benefits VS "AS-IS" Cloud Migration
- 11. Raising the BAR
- 12. Landscape