Server-side WebAssembly

Server-side WebAssembly Horacio Gonzalez 2021-06-24

Who are we? Introducing myself and introducing OVH OVHcloud

Horacio Gonzalez @LostInBrittany Spaniard lost in Brittany, developer, dreamer and all-around geek Flutter

OVHcloud: A global leader Web Cloud & Telcom 30 Data Centers in 12 locations 1 Million+ Servers produced since 1999 Private Cloud 34 Points of Presence on a 20 TBPS Bandwidth Network 1.5 Million Customers across 132 countries Public Cloud 2200 Employees worldwide 3.8 Million Websites hosting Storage 115K Private Cloud VMS running 1.5 Billion Euros Invested since 2016 300K Public Cloud instances running P.U.E. 1.09 Energy efficiency indicator 380K Physical Servers running in our data centers 20+ Years in Business Disrupting since 1999 Network & Security

Did I say WebAssembly? Wasm for friends…

WebAssembly, what’s that?

A low-level binary format Not a programming language, a compilation target

That runs on a stack-based virtual machine A portable binary format that runs on all modern browsers… but also on NodeJS and elsewhere!!

With several key advantages

But above all… Wasm is not meant to replace JavaScript

Who is using WebAssembly today? And many more others…

A bit of history Remembering the past to better understand the present

Executing other languages in the browser A long story, with many failures…

2012 - From C to JS: enter emscripten Passing by LLVM pivot

2013 - Generated JS is slow… Let’s use only a strict subset of JS: asm.js Only features adapted to AOT optimization

WebAssembly project Joint effort

Server-side WebAssembly Too good to not to use it

Solomon on Web Assembly

A very interesting feature set

Features of Wasm Why is everybody looking at it?

Near native speed https://medium.com/wasmer/benchmarking-webassembly-runtimes-18497ce0d76e

Highly portable It can be run almost everywhere…

Readable and debuggable Each .wasm file with it .wat companion file

Memory safe & secure Running in a fully sandboxed environment

Accepting many source languages And more and more…

Still a young platform… But growing up fast!

Native WASM types are limited WASM currently has four available types: ● i32: 32-bit integer ● i64: 64-bit integer ● f32: 32-bit float ● f64: 64-bit float Types from languages compiled to WASM are mapped to these types

How can we share data? Using the same data in WASM and JS? Shared linear memory between them, and serializing the data to one Wasm types

Solution is coming: Interface types Beautiful description at: https://hacks.mozilla.org/2019/08/webassembly-interface-types

No outside access By design, communication is done using the shared linear memory only

Solution exists: WASI

Mono-thread and scalar operations only Not the most efficient way…

Solution exists: SIMD

Solutions are coming too: Wasm Threads Threads on Web Workers with shared linear memory

Incoming proposals: Garbage collector And exception handling

The Bytecode Alliance Taking WASM out of the browser

The Bytecode Alliance

Bytecode Alliance projects

Wasmtime

Cranelift

WebAssembly Micro Runtime (wamr)

Lucet

Other runtimes Runtimes, runtimes everywhere

Wasmer Run any code* on any client… almost * Languages compiling to WASM

Wasmer

Wasmer ecosystem

Wasm3

And even Wasm over GraalVM!

Or in Kubernetes…

Some examples IRL? Like companies using these things

Cloudflare Workers (FaaS)

Fastly works on the edge of the cloud

Clever Cloud FaaS infrastructure https://www.youtube.com/watch?v=wchehMIsu80

Clever Cloud FaaS Infrastructure Already used in internal projects Able to execute complex loads (neural networks models)

Clever Cloud FaaS Infrastructure Blazing fast

That’s all, folks! Thank you all!