You Say MicroServices - I say Unikernels

A quick look at how unikernels not only embrace microservices and immutable infrastructure but also dispels myths around debugging and performance concerns.

Transcript

1. You Say MicroServices - I say Unikernels
2. immutable infrastructure
4. burn ami
5. artifacts don’t change once deployed
6. microservices
7. Micro-Services
9. isolation
10. Is Linux Isolated? No
11. are containers isolated? Nein
12. why do we care?
13. hint: not just security
14. manageability
15. security
16. devops
17. pagerduty alert
18. ulimits are off?? -bash: fork: retry: Resource temporarily unavailable -bash: fork: retry: Resource temporarily unavailable -bash: fork: retry: Resource temporarily unavailable -bash: fork: retry: Resource temporarily unavailable -bash: fork: retry: Resource temporarily unavailable -bash: fork: retry: Resource temporarily unavailable -bash: fork: retry: Resource temporarily unavailable -bash: fork: retry: Resource temporarily unavailable
19. only vim? sudo apt-get install emacs
21. 2 weeks later
24. debugging
27. gdb
33. WHERE’S MY SHELL DOOD?
35. performance
38. 406k Requests/Second
41. single address space
42. no context switching
43. linux
45. 0xAA55 Let’s boot some unikernels
46. https://deferpanic.com https://github.com/deferpanic/virgo http://www.meetup.com/San-Francisco-Unikernels/