4 ms·
Reminds me of an idea: instead of having lots of orthogonal endpoints or using GraphQL, accept WASM modules as requests and provide the service as functions in
by Kinrany 2y ago
Reminds me of an idea: instead of having lots of orthogonal endpoints or using GraphQL, accept WASM modules as requests and provide the service as functions in the WASM environment.
- meindnoch 2y agoGreat idea! This would enable users to pass arbitrarily complex queries to the server, without introducing new endpoints for each use case. This is the genius of WebAssembly! Later we could also add some "default" query language on top of WASM, so you wouldn't have to fire up a proper compiler for simple queries. We could call this language e.g. Simple Query Language? Could be shortened as SQL. Like I said, this is the genius of WebAssembly!
- Kinrany 2y ago"All new ideas are dumb because they're a little bit like the old ideas", great take
- nilslice 2y agoYes! Especially with the ability for wasm code to call host-provided import functions, the module can do lots of really interesting things. Here’s an example that might be interesting: https://nordicapis.com/beyond-the-http-api-webassembly-and-the-future-of-systems-integration/ https://nordicapis.com/beyond-the-http-api-webassembly-and-t... (skip down to the part about Stripe and how a wasm integration pattern can power much more sophisticated bi-directional interactions).