From d3dfec6f52d8093db276adb62021ced8f58e590c Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Sun, 5 Nov 2023 12:17:03 +0100 Subject: Added lazy loading to images --- _posts/2021-12-25-running-golang-application-as-pid1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '_posts/2021-12-25-running-golang-application-as-pid1.md') diff --git a/_posts/2021-12-25-running-golang-application-as-pid1.md b/_posts/2021-12-25-running-golang-application-as-pid1.md index 1f67ee1..edd5a57 100644 --- a/_posts/2021-12-25-running-golang-application-as-pid1.md +++ b/_posts/2021-12-25-running-golang-application-as-pid1.md @@ -24,7 +24,7 @@ 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](/assets/posts/pid1/unikernels.webp) +![Virtual machines vs Containers vs Unikernels](/assets/posts/pid1/unikernels.webp){:loading="lazy"} 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 -- cgit v1.2.3