6. Some Background
• Containers started out at Sun in the 90s.
• They are an extension of traditional OSlevel isolation primitives, including filesystem ACLs, to control access to shared
physical resources.
• They have matured with network
namespaces and overlay filesystems
7. Docker: Making containers
easy command line tools
• Great
• Well-integrated overlay filesystems
• Well-integrated network management
8. So… containers via Docker
Pros:
• Wickedly fast
• Simple to deploy
• Abstracted from
the base OS
Cons:
• No windows
• No *nix
• Doesn’t address
the hard
problems (multiserver, multi-tier,
in-place
upgrades, or HA)
9. So why is it so popular!?
• UX matters.
• UX matters… a LOT.
•
•
•
•
Built-in emulator for learning.
Built-in hosted image repository.
Good json output.
Really damn easy install.
14. What isn’t PaaS?
• It’s not the method of isolation
• It’s not the operating system
What is PaaS?
• Automation of app placement & scaling
• Orchestration of services and
infrastructure
17. Takeaways
• Everything in cloud competes with
everything else, at a 40% overlap.
• Most PaaS use some kind of process
isolation (containers or whatever)
internally.
• The process isolation isn’t the hard part.
• UX matters.