Unikernels are young, and lack tooling/robustness that we have in more traditional approaches. They are not production ready yet, but will likely become a prominent way of building and deploying applications in the future.
Unikernels are young, and lack tooling/robustness that we have in more traditional approaches. They are not production ready yet, but will likely become a prominent way of building and deploying applications in the future.
> Unikernels are unfit for production not merely as implemented but as conceived: they cannot be understood when they misbehave in production — and by their own assertions, they never will be able to be.
* High performence overhead and complexity of VM.
* Hypervisor vulnerabilities.
* Unikernel are small because the responsibilities are shifted to the process.
* "Unikernels are entirely undebuggable."
---
IMO process isolation (segmentation, paging etc) already gives 100% performence with most security. And since these are old and simpler hardware designs, hardware bugs are less likely to happen.