4 ms·
Depends, is your code being served to the internet? If it is I would definitely consider firecracker but if its just internal it probably won't matter a whole l
by alan-hn 5y ago
Depends, is your code being served to the internet? If it is I would definitely consider firecracker but if its just internal it probably won't matter a whole lot. Not sure about the overhead of docker compared with firecracker though, so there may be advantages there either way.
There's also ignite which works with firecracker:
https://github.com/weaveworks/ignite https://github.com/weaveworks/ignite
- kennethh 5y agoAnyone tried Ignite out? Looks like a cool project but I tried to search around but did not fint much about it.
- alexellisuk 5y agoIgnite will launch a microVM in a similar way to my lab, except it has a user experience designed more around Docker's CLI. Great if you just want to use it like a black box. If you're more interested in integrating with Firecracker into your own systems - come to the session because I'm covering this in detail. Weaveworks is now working on a new tool to create K8s clusters where each node is a microVM - Richard Case will be doing a demo of that, and it's super fast. It's for a Telco customer they have, so it's a real use-case, not just shiny tech, so should score extra points, right?