What have you learned from using WebAssembly as sqlc’s plugin boundary?

[NICE-DEV226]

Hi!

I came across sqlc’s WebAssembly plugin system while working on my own Go project, Dun.

Dun is an experimental Go-native HTTP data plane where application-specific behavior runs as Wasm extensions. I’m exploring Wasm as the extension boundary because it gives me isolation, explicit capabilities, and the possibility to write extensions in different languages.

The approach in sqlc caught my attention because you’re already using Wasm for a real plugin system.

I’d be interested to hear what you’ve learned from it so far, especially any limitations or design decisions you would change with what you know today.

Dun: https://github.com/NICE-DEV226/Dun