Build Database Driven Applications in Wasm by Michael Yuan @ Wasm I/O 2023

Wasm I/O 2023 / 23-24 March, Barcelona
Slides: 2023.wasmio.tech/docs/session...
Wasm has emerged as a secure, portable, lightweight, and high-performance application runtime for cloud-native workloads such as microservices and serverless functions. However, the standard Wasm sandbox does not readily support database connections. The Wasm community has created several solutions to address the diverse use case scenarios for database applications. There are three important approaches.
- Use host functions, such as Spin framework and the upcoming component model framework, to handle database connections outside of the VM and expose the data through APIs to Wasm guest apps.
- Support existing database client libraries and drivers in Wasm guest apps through WASI-like socket APIs.
- Embed the Wasm VM into a data pipeline and exchanged data with the Wasm guest app through shared memory space.
Each of these approaches has pros and cons. In this talk, we will present examples of Wasm apps connecting to MySQL, TiDB, and Redis, databases. We will also discuss database UDF and ETL use cases built on Wasm functions.

[@tklightningfast8326]

I'm confused; why the need to put it into a docker container if the service is written in Wasm? Wasn't the whole point of Wasm to abstract away the CPU, like Docket did but in a more lightweight way?

[@officialismailshah]

I think this video will help you th-cam.com/video/7553XZ0T6pM/w-d-xo.html

[@gaubeebangeel4251]

He mentioned that the machine didn't even have a rust environment, so it was probably just a temporary machine used for presentations. Therefore, installing a docker can simplify many problems.