Better together: A Kubernetes and Wasm case study
Adobe design tools are (necessarily) complex and powerful beasts, for this reason, they have always been a pioneer of bringing desktop applications to the web, they were the creators of Flash after all! More recently they have very much embraced WebAssembly, back in issue #159 we reported that they are bringing Photoshop to the web.
Adobe are also very interested in how they can leverage WebAssembly on the server-side. This blog post details some recent projects where they have been looking at how to incorporate WebAssembly into their existing Kubernetes-based architecture. In the first example they share how they ported a background-image-removal function to run on wasmCloud, with promising results. They have also been looking at hoe to run entire microservices using the same platform.
Whilst there is growing excitement about the use of WebAssembly on the server, we have to acknowledge that it is early days for the technology, which is why hearing about the successes Adobe are having with this technology are so important. They validate the direction of travel.
Threads and Messages with Rust and WebAssembly
Concurrency is hard, threads are hard, which is why so many of us love the single-threaded comfort of environments like Node and the browser! This blog post takes a practical look at Web Workers and WebAssembly shared memory, hopefully this will point you in the right direction.
Go vs Rust vs AssemblyScript