embly VS grafbase

Hey, I tried to build something like this too: https://github.com/embly/embly

My takeaway after building that is that the build tooling is the major pain point. If you're trying to onboard someone onto this platform from their favorite language the hard part is getting from code to the .wasm file. wasm-bindgen (as an example) has put so much effort into build tooling, I wonder if that's a necessary path for success here.

It's also great that WASI exists now, if I had to do embly again I'd just use wasi and then implement all of my "platform" features as filesystem features, not syscalls. If your API interface is the filesystem then you could provide interoperability between environments. Let's say you want to include a key-value store in the wasi runtime, you just make the keys files and the values file contents. Then you could so something like ship a FUSE filesystem to interact with the filesystem in the same way from a traditional VM or on a personal computer. I got really bogged down in custom syscalls and this path seems potentially more elegant.

Have you also thought about live process migration? I got really excited about this from a technical standpoint. Since you completely control the runtime you could set up a clustered wasm solution that moves long running processes from VM to VM by sending their live memory state to another machine. Not sure if that's actually useful, but cool that it's not bogged down by the usual complexities of doing the same in a full OS environment.

Anyway, so glad to see that someone is taking this idea on. Please make a cloud platform and let me pay for it. Also happy to chat more if any of this is useful, I've joined your discord as "max".

Grafbase (GraphQL)

https://github.com/grafbase/grafbase/tree/main/examples/reso...

Founder of Grafbase here.

From a product perspective Grafbase offers a serverless, realtime GraphQL API deployed at the edge. Our goal is to provide a unified data layer on top of existing APIs and databases.

The Grafbase platform itself is built in Rust and deployed to the edge using WebAssembly. Every GraphQL endpoint is deployed to V8 isolates at the edge which translates to very low cold starts and extremely fast performance globally.

Our branching feature makes collaboration seamless with your team. Just created a Git branch and push it up to create an instant preview branch that is totally isolated from production.

The Grafbase CLI is open source and available on GitHub: https://github.com/grafbase/grafbase.

Check us out: https://grafbase.com/

We are Grafbase are making backends easy. Using the CLI, you can use the entire platform (including live queries) locally.

Grafbase was built to manage all of the above. You get a distributed GraphQL API at the edge by creating a single grafbase/schema.graphql file in your project.

The Grafbase CLI is written in Rust and open-sourced on GitHub.