WASM vs Docker Containers vs Kubernetes vs Serverless: The Battle for Cloud Native Supremacy

This video explores WASM and compares it with Docker containers, Kubernetes, serverless, and edge to answer the following questions.
- What is WASM?
- Should we use it in browsers?
- Should we replace Docker containers with WASM?
- Should we run it in Kubernetes clusters or replace Kubernetes altogether?
- Is it the future of serverless computing and edge devices?
- Why should we use WASM and, if yes, where should we use it?

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Sponsor: Cast AI
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

#wasm #webassembly #wasi

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction to Web Assembly (WASM)
00:54 Sponsor: CAST AI
01:35 What is WebAssembly (WASM)?
05:59 WebAssembly (WASM) in Servers
10:18 WASM vs. Docker (Containers)
15:47 WASM vs. Kubernetes
19:33 WASM vs. Serverless
21:31 WASM on Edge
22:14 Why WASM? Should You Use WASM? Where To Use WASM?

[DevOpsToolkit]

Are you using WASM? If you are, what are the use-cases where it shines?

[josefromspace]

Bright future ahead for WASM, sometimes waiting for its maturity is the best thing we can do for a technology. Great video as always.

[LearningIsfun]

Currently experimenting with web apps using kotlin and jetpack compose! I wouldn't say I'm too impressed but there is a huge potential especially now that the compose is not optimised for wasm but it already seem fast.

[sergeyp]

Judging by the information I found in the web (not tested it yet, though), WASM is already integrated in containers/kubernetes world: WASM modules can be packaged as OCI images and run by containerd with runwasi runtime plugin. Kubernetes already have support for arbitrary RuntimeClasses, so there must be no big dial to run WASM pods alongside with classic ones (based on runc runtime).
On the other hand, same runtime plugin system can also made traditional containers more secure the same way as WASI - by inserting protective runtime layer between binary and OS kernel, as gVisor (runcs runtime plugin) does.
Finally, can't say that typical container images needed more than two OS/arch variants: Linux/amd64 (includes Intel) and Linux/arm64. All containers I've seen on Windows was run in Docker Desktop, which is just VM with Linux inside :) Heard about native Windows containers, but never seen these in practice.

[mihaigalos]

WASM is relevant if i.e. you want native performance in a browser, that's where it shines: 3D graphics rendering written in i.e. C++ directly in Chrome or similar.

[IvanRizzante]

Thanks for another great video! It looks definitively promising, will see about it.

[cowgod]

Thanks diving into this topic. I've been wanting to learn more about this buzzword I keep hearing, and I now feel much better informed about the subject, and whether it's worth consideration for my projects in the future.

[suikast]

Great talk thanks

I am using nomad and work in past with k3s.

Can you please share your expression nomad I dont understand your crititic at last point.

[Luther_Luffeigh]

I’d love to see K8s supporting Wasm runtimes sometime in this decade, but knowing how K8s progress on major changes, I’m not holding my breath. I have seen articles of successful adoption of Wasm runtimes in HashiCorp Nomad with little effort.

[codecrafter_]

In my experience crossbuilding containers can take a long time and compiling them once to WASM and run them managed on Kubernetes is a nice choice

[cramhead]

It might be interesting to look into WASM on docker

[RichardQuadling]

Before 3:29, the idea of Flash was what WASM could have been!

[afewell]

I know its not the same as wasm, but I am very interested in wasmclouds nat overlay network. I think the concept that an optimized m2m messaging protocol could make a lot of sense for distributed microservices applications. Some of the examples I have seen of messaging performance are extremely powerful, and the features you get as a result from a networking perspective are pretty magical. Regardless of the merits of these claims. the big problem is apps need to be written specifically for wasmcloud which of course doesnt invalidate it, just makes the addressable market much smaller as it can only be considered with new apps or drastic refactorings. Perhaps my biggest question with this is should we be more aggressive in exploring alternative network tech for microservice-to-microservice comms whether it be wasmcloud or maybe changing app code further to build m2m messaging around primitive nats constructs, or aside from nats, just given the radical performance deltas it has for certain messaging use cases, should we be focusing more on other alternative network approaches whatever they may be as clearly there seems potential to unlock some big benefits.

[Farrukhw]

I think the K8 and containers are more flexible in terms of customizations...
WASM seems to be acting like an API (but not exactly, I know) and can also be make part of a Container...

[ZiggleFingers]

native compiled code will always be faster than wasm. wasm runs in a virtual machine, so it is java lite. it will be faster than python or javascript - so use it if your existing codebase is written as such and want a performance gain - especially if you have no idea how to package a container. but if your product is performance oriented you've already probably written it in an appropriate language, and it will be 2x-12x+ faster than wasm as a architecture native binary.

Wirth's law: software is getting slower more rapidly than hardware is becoming faster.

[ch.hayabusa]

So the main takeaway is, I should move to Liechtenstein

[renanmonteirobarbosa]

You are only considering one type of container standard, the OCI. You are ingnoring SIF containers

[lhxperimental]

Java implemts the same idea. The pendulum has swung back.