Unikernels: when you should and when you shouldn't
•
0 likes•198 views
As with all technology, there are trade-offs with unikernels. This talk considers the benefits & drawbacks. By stepping away from hype & clarifying misunderstandings, attendees will appreciate why unikernels exist & where they're going. Attendees will also have a better idea of when they should consider a library OS for their next project, as well as the trade-offs they'll need to consider.
Recommended
More Related Content
Viewers also liked
Viewers also liked (11)
Similar to Unikernels: when you should and when you shouldn't
Similar to Unikernels: when you should and when you shouldn't (20)
Recently uploaded
Recently uploaded (20)
Unikernels: when you should and when you shouldn't
- 1. Unikernels! When you should and when you shouldn’t ContainerCon EU 6 Oct 2016 @amirmc Amir Chaudhry … on behalf of many others!
- 2. About me @amirmc Work at Docker … in Cambridge, UK I have more hair on my face since this pic
- 4. …is an application … Software today… @amirmc
- 5. …is an application … … on top of an Operating System. Software today… @amirmc
- 8. Code you care about Code the OS insists you need @amirmc
- 9. Code you care about Code the OS insists you need @amirmc
- 10. Software today… … is built locally… @amirmc
- 11. Software today… … is built locally… … but deployed remotely… @amirmc
- 12. Software today… … is built locally… … but deployed remotely… @amirmc … very remotely.
- 14. Software today… …is complex! Even though most apps are single-purpose @amirmc
- 15. Complexity is the enemy… More pieces -> tricky config Duplication -> inefficiency Large sizes -> long boot times More stuff -> larger attack surface @amirmc
- 16. Things are getting easier
- 17. BUILD Developer Workflows SHIP Registry Services RUN Management Docker for Mac and Docker Trusted Registry Docker Universal Control Plane Docker Cloud Docker Container Engine Ecosystem Plugins and Integrations Docker Containers as a Service Platform
- 18. An extreme view? Disentangle applications from the OS Break up OS functionality into modular components Link only the system functionality your app needs Target alternative platforms from a single codebase @amirmc
- 19. An extreme view? Disentangle applications from the OS Break up OS functionality into modular components Link only the system functionality your app needs Target alternative platforms from a single codebase Unikernels! @amirmc
- 20. Unikernels Model is “Just enough OS” for your specific app. https://en.wikipedia.org/wiki/Unikernel @amirmc Using a modular stack, every application is compiled into its own specialised OS, targeted for the cloud or embedded devices
- 22. Continuum Disentangle applications from the OS Break up OS functionality into modular components Link only the system functionality your app needs Target alternative platforms from a single codebase @amirmc
- 23. • LING • MirageOS • OSv • Rumprun • runtime.js • ClickOS • Clive • Drawbridge • HaLVM • IncludeOS @amirmc Unikernels
- 27. MirageOS
- 30. MirageOS @amirmc
- 31. unikernel} MirageOS Familiar development cycle Broad deployment scenarios @amirmc
- 32. unikernel} MirageOS Familiar development cycle Broad deployment scenarios Target different environments Your usual tools @amirmc
- 33. Demo: Build on a Mac Deploy to IoT @amirmc
- 34. • Build and run an app in a Linux container • Retarget app for ARM backend • Deploy artefact onto an ARM device @amirmc
- 35. Demo: 2048 game
- 37. • Built and ran an app in a Linux container! • Retargeted app for ARM backend! • Deployed artefact onto an ARM device! @amirmc
- 38. • Rewrote TLS • Functional core • Less code Bitcoin Piñata
- 41. 8.2MB Unikernel 102 kloc 2560 kloc ~200MB Full OS Contains everything No extra stuff! Much smaller attack surface
- 42. 8.2MB Unikernel 102 kloc 2560 kloc ~200MB Full OS Contains everything No extra stuff! Much smaller attack surface
- 43. Unikernel Recap • Highly specialised • Continuum with containers • Robust deployments • Everything’s a library! @amirmc
- 44. Deployments
- 45. Deployments
- 46. Deployments
- 47. So when should you use them?
- 48. Software today… …is complex! @amirmc … but it depends. Complexity is relative (kind of) Complexity is the enemy…
- 49. Right tool for the job @amirmc
- 50. • Single ‘service’ • Distributed system • Independent deployment • Diversity of tech choices Unikernel Properties Microservices @amirmc
- 52. Monolith
- 53. Monolith
- 55. Microservices
- 60. “Hands on” Are you a mechanic? “Works out of the box” Seeking convenience? @amirmc
- 61. unikernel.org Still early days! Thanks for listening! Questions?