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"
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