wasm workers running inside browser or server using capsule architecture

[gedw99]

I am amazed there is not more discussion here, because capsule look really good.

I would like to build up gaoling code such that we can run the same nano worker in a browser as well as in capsule.

so then you can deploy you app to the server or the client. which h means we also get the ability to server search bits from the server, but then upgrade clients with the same warm and so give human users a paw like experience.

the interesting aspect of this is that there is a type of bus between a browser window and the web workers, just like there is the NATS bus between the workers. so I am thinking about how we can have a bus that is agnostic to if its running on the server or c client (browser).

[gedw99]

then you think about what's available as core std services on the server and client.

A bit like what cloud flare works provides. a google example in golang is here. https://github.com/syumai/workers#features

A unified one in GOLANG is here. https://github.com/hack-pad/hackpadfs

• can run in browser (as warm) or on the server.
• has kv , just like NATS kV. so we have a client side and server side offering.
• has fs which can be called buckets, just like NATS object store. so we have a client side and server side offering.

[k33g]

@gedw99 I'm not sure to understand:

• The wasm module produced to be executed by Capsule targets wasi, so it's not possible to run in a browser
• The Capsule wasm module is linked to the launcher (Capsule) because of the host functions (for example, the handler), and the browser cannot bring these hosts functions