From ae24d9a8869c497537839f330384cbadb2cf687c Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Tue, 31 Oct 2023 10:17:43 +0100 Subject: Updated theme --- public/running-golang-application-as-pid1.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'public/running-golang-application-as-pid1.html') diff --git a/public/running-golang-application-as-pid1.html b/public/running-golang-application-as-pid1.html index 12877be..3047555 100755 --- a/public/running-golang-application-as-pid1.html +++ b/public/running-golang-application-as-pid1.html @@ -13,7 +13,7 @@ idea, it makes a lot of sense.

A unikernel is a specialized, singl by using library operating systems. (Wikipedia)

I really like the explanation from the article Unikernels: Rise of the Virtual Library Operating System. Really worth a read.

If we compare a normal operating system to a unikernel side by side, they would -look something like this.

Virtual machines vs Containers vs Unikernels

From this image, we can see how the complexity significantly decreases with +look something like this.

Virtual machines vs Containers vs Unikernels

From this image, we can see how the complexity significantly decreases with the use of Unikernels. This comes with a price, of course. Unikernels are hard to get running and require a lot of work since you don't have an actual proper kernel running in the background providing network access and drivers etc.

So as a half step to make the stack simpler, I started looking into using @@ -184,11 +184,11 @@ and could be deployed to AWS as an EC2 instance and observing how it fares. But in that case, we would need to write some sort of supervisor that would run on a separate EC2 that would check if other EC2 instances are running properly. Remember that if your application fails, kernel panics and the -whole machine is inoperable in this case.

Posts from blogs I follow around the net