Unikernels and why they're useful (or not)
summary
Demo shows a real OCaml app compiled with MirageOS and built inside Docker containers then retargeted from a Unix process to an ARM unikernel and deployed to a tiny board, the 2048 game running unchanged. A static site example compiles to about 8.2 megabytes and about 4% of the original LOC. A public challenge holds ten bit coins for over a year despite tens of thousands of attacks, proving resilience.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:58Modern software complexity
- 3:54What are unikernels
- 5:22Unikernels vs containers
- 7:33Legacy vs clean-slate
- 8:21Live demo: 2048 game
- 16:16Demo recap and ARM
- 17:44Code reduction and security
- 18:28Real-world deployments
- 20:28Libraries and Docker
- 20:50When to use unikernels
- 21:58Monoliths to unikernels
- 23:07Production readiness
- 24:37Getting started
- 25:01Q&A
related talks
01h 06mCompile your own cloud with Mirage OS v2.0
43mClimbing out from the digital mud with unikernels
33mNon-Imperative Network Programming
30mBeyond Orchestration: The Cloud Native Runtimes Ecosystem for Performance and Security
22mThe Irresistible Rise of Cloud Native: What the Future Means for YOU
38mSecure Containers in Embedded Deployments
32mClosing Keynote: The Joy and Excitement of Forbidden Computer
10murunc: A container runtime for unikernels and single application kernels