Virtualization, Containers and Clouds

A quick walk-through in virtual machines and how containers have resolved a performance issue. Additionally, a quick hint about managing clouds and an example with Docker are added.
This presentation is simply showing the concept, with no technical details.

Transcript

1. Virtualization, Containers and Clouds A brief history -- Tarek ELDEEB
2. Bare Metal Computer Setup • No IT knowledge required • Easy for a 1-time setup • Best Performance! • Low utilization → High Cost • Some apps are vulnerable → Expose others • Some apps crash → System may go down! • Setup is not extendable (Add RAM, Storage, .. etc) • Setup is not highly available (Use UPS?) • Setup is hardly duplicatable, no load-balancing
3. Virtual Machines Setup • No Little IT knowledge required • Easy for a 1-time setup • Best Worst Performance! • Low utilization → High Cost • Some apps are vulnerable → Expose others • Some apps crash → System may go down! • Setup is not extendable (Add RAM, Storage, .. etc) • Setup is not highly available (Use UPS?) • Setup is hardly duplicatable, no load-balancing 1960s → Patented by IBM (Mainframes) 1990s → Revived by VMWare (VPS) 2000s → Open source: VBox
4. Virtual Machines in the Cloud • No Little More IT knowledge required • Easy for a 1-time setup • Best Worst Performance! • Low utilization → High Cost • Some apps are vulnerable → Expose others • Some apps crash → System may go down! • Setup is not extendable (Add RAM, Storage, .. etc) • Setup is not highly available (Use UPS?) • Setup is hardly duplicatable, no load-balancing 2010s → AWS, Azure, VMWare, ..
5. Containers Setup • No Little More IT knowledge required • Easy for a 1-time setup • Best Worst Good Performance! • Low utilization → High Cost • Some apps are vulnerable → Expose others • Some apps crash → System may go down! • Setup is not extendable (Add RAM, Storage, .. etc) • Setup is not highly available (Use UPS?) • Setup is hardly duplicatable, no load-balancing 2013 → Docker
6. Containers in the Cloud • No Little More IT knowledge required • Easy for a 1-time setup • Best Worst Good Performance! • Low utilization → High Cost • Some apps are vulnerable → Expose others • Some apps crash → System may go down! • Setup is not extendable (Add RAM, Storage, .. etc) • Setup is not highly available (Use UPS?) • Setup is hardly duplicatable, no load-balancing 2015 → Kubernetes by Google 2016 → Launch Cloud Native Computing Foundation
7. Next Setup: Service-based (Serverless) • Solution is not server-bounded! • Different HW setups exist in the pipe! • Cost Effective, extendable, ..etc • Scripting and Glue logic are new required skills • Programming and IT are coming closer
8. • Similar to git commands • Building new containers may be the last part of a CI workflow • A container may include a large stack, with libs, support tools, runtime environments .. etc. Bonus: Docker Hub Workflow
9. References https://slideplayer.com/slide/10184624/ https://knowledge.kitchen/mediawiki/index.php?title=Introduction_to_containers https://www.docker.com/why-docker https://en.wikipedia.org/wiki/Cloud_Native_Computing_Foundation https://www.alibabacloud.com/blog/serverless-vs--traditional-architecture-what-are-the-differences_594578 https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/