How the hell did we end up here? The evolution of cloud, microservices and virtualization
•Download as PPTX, PDF•
0 likes•185 views
From timeshared workloads on the IBM CP-40 in 1965 to Linux containers running on SmartOS hosts on bare metal blade hardware in 2015, the industry has come a long way in half a decade, radically changing the way hardware and software are designed. Modern professionals take architectural patterns such as microservices, serverless and container-oriented for granted. Sometimes to understand why we build modern applications the way we do, and what problems these patterns really solve, it helps to follow the evolution of these styles in terms of hardware, software and architectural milestones along the way. In this presentation, we’ll take a walk down memory lane to discover how the hell we ended up here.
Recommended
Recommended
More Related Content
Similar to How the hell did we end up here? The evolution of cloud, microservices and virtualization
Similar to How the hell did we end up here? The evolution of cloud, microservices and virtualization (20)
Recently uploaded
Recently uploaded (20)
How the hell did we end up here? The evolution of cloud, microservices and virtualization
- 1. Cloud, Microservices & Virtualization How the hell did we end up here? Issac Goldstand Principal Enterprise Architect
- 3. The growth of the data center...
- 4. A challenge arises How can I reduce my hardware footprint without compromising performance?
- 5. 1965 - IBM CP-40
- 6. 1979 - Version 7 UNIX
- 7. 1979 - Version 7 UNIX
- 8. Late 1980s
- 9. 1993 - Linux 0.99
- 10. 1993 - Oslo University
- 11. 1994
- 12. 1996 - Gartner
- 13. 2000 - FreeBSD 4.0
- 14. 2001 - VMWare
- 15. 2001 - RLX Technologies
- 16. 2002 - Linux 2.4.19
- 17. 2003 - University of Cambridge
- 18. 2005 - Solaris 10
- 20. 2005
- 21. 2004
- 22. 2006
- 23. 2006 - VMWare ESX 3.0
- 24. 2006 - AWS S3 + EC2
- 25. 2007/8 - Linux 2.6.24
- 26. 2008 - Agile 2008 Toronto
- 27. 2008
- 28. 2012 - Martin Fowler
- 29. 2013 - dotCloud
- 30. 2014 - Linux 3.18
- 31. 2014 - Martin Fowler & James Lewis
- 32. 2014 - Docker, Inc
- 33. 2014 - AWS
- 34. 2015 - Docker 0.9
- 35. 2015 - Joyent
- 36. Going forward...
- 37. Thank You
Editor's Notes
- Speaker notes go here
- Installation of the first computer with a 5kb memory, Weizman Institute, Israel, 10-16-1955
- The first Hypervisor released
- Initial support for chroot jails. Restrict FS access
- Union mounts in Plan 9, SunOS, BSD Unix
- UnionFS hits the linux kernel
- cfengine written by Mark Burgess to automate management of his workstations
- Amazon.com launches an online bookstore
- Gartner articles “Service Oriented” Architecture Part 1/2
- FreeBSD jails adds independent hostnames, independant networking (by default) and independant users
- VMWare ESX (type 1) and GSX (type 2) launched
- The first commercial Blade Server relieves datacenter density. In 2014 42U holds 1440 blades per cabinet
- Namespaces: mnt, pid, net, ipc, user
- Opensource Xen (type 1) released
- Fully integrated in the OS. Complete mini-OS in the OS. Kernel translation for other langauges
- ZFS including snapshotting and CoW
- Puppet is born
- Joyent is born
- AUFS introduced to replace UnionFS
- Live migration of VM between hypervisors. First CPU/RAM; then storage, too
- EC2 in August, S3 in March
- Google cgroups (process containers) Resource limits, prioritization, quota/accting, control
- Patrick Debois presents “Agile Infrastructure & Operations” which presents the idea now dubbed DevOps
- LXC 0.1 is released
- The “pheonix server” dies and rises from the ashes - this later becomes Immutable Server
- Docker (LXC)
- OverlayFS merged into Linux
- Martin Fowler & James Lewis define “Microservice Architecture”
- Public docker registry
- AWS launches Elastic Container Service
- Docker libcontainer → runc
- Joyent launches Triton with docker support - Does this mean that I’ll be able to DTrace my Linux apps in a Docker container?