We've got containers running for each instance of the runtime a user needs. And for now we just keep them running forever as long as the project is up. But that's very inefficient, and we're definitely looking for a better way to do it.
Hey, Damien here, author of the article! Real happy you like it!
We initially thought about running tokio in wasm (they've added support for WASI recently as well IIRC), but elected against it because we found it just moved the compile time problem from one compilation target to another.
So in the end we decided to go with the second option. So when the guy in the example `.await`'s, context can go back to the runtime. But inside wasm this is not tokio, this is our own shim to the executor running on the outside.
Synth (YC S20) [1] is an open source declarative data generator written 100% in Rust.
We are looking for someone with prior experience writing Rust in production for a 1-to-3 months contract to work with us on our core open-source project.
- Proven experience writing production Rust code, preferably in a large code base
- Knowledge of PostgreSQL at a level sufficient to design and build reliable integration
- Strong knowledge of data structures and algorithms
- Track record of contribution to open-source projects, preferably on GitHub
- Ability to work quickly and rigorously in a fully remote setting
If that sounds interesting, we want to talk to you! Shoot me an email at damien [at] getsynth.com!
We've got containers running for each instance of the runtime a user needs. And for now we just keep them running forever as long as the project is up. But that's very inefficient, and we're definitely looking for a better way to do it.