Porting Projects to Unikernels When you Don't Know the Language and Don't Know the Project

Many projects don't require porting for unikernels but some do. Some also have upfront configuration work you might have to do similar to building a dockerfile from scratch.
In this video we show an example of the process on how we go about porting projects, such as the n8n workflow automation tool, to unikernels when we don't know the language and don't know the project.

[@atrocitus777]

my brain understands kubernetes can scale container applications how would you scale unikernels?

[@nanovms7360]

Good question and it's something *everyone* has trouble grokking until they push their unikernels to the cloud for the first time. Essentially kubernetes exist because you need something to deal with networking and storage and things of that nature. However, unikernels are virtual machines at the end of the day, albeit just specialized ones, and so they get to re-use all the existing primitives that every single cloud providers has. That is - while you configure your unikernel to your hearts content you don't actually manage the networking and storage and such of it. The clouds do. So to scale you spin up as many instances you need or want and if you're unsure and want to use something like auto-scaling-groups that just works out of the box.