e2core

Thanks for this as I was also wondering about network partitioning, and all those failure fun and games that distributed systems must handle. This golang package helps to remedy that by providing a bus / messsge queue that can run in process or over the network. So you get rpc without thinking about it and failure is managed by the data plane forwarding the message when the network is healthy again. https://github.com/suborbital/e2core/blob/main/foundation/bu... This however forces all other code using a package like this to adapt to the realities that you’re in an async non blocking world now. A rpc call will give you a response eventually. So the calling func and all parent funcs will just have to wait around when the network is unhealthy?

> If one writes Go or Rust, there are much better ways to run them than targeting WASM wasm has its place, especially for contained workloads that can be wrapped in strict capability boundaries compile-time (think, file-encoding jobs that shouldn't access anything else but said files: https://news.ycombinator.com/item?id=29112713). > Containers are still the defacto standard. afa FaaS is concerned, wasmedge [0], atmo [1], tarmac [2], krustlet [3], blueboat [4] and numerous other projects are turning up the heat [5]! [0] https://github.com/WasmEdge/WasmEdge [1] https://github.com/suborbital/atmo [2] https://github.com/madflojo/tarmac [3] https://github.com/krustlet/krustlet [4] https://github.com/losfair/blueboat [5] https://news.ycombinator.com/item?id=30155295

Thanks for the explanations. What is that wasm project you're working on, if it has been publicly announced / released? It sounds very similar to Microsoft's Krustlet.dev and Suborbital's Atmo: https://github.com/suborbital/atmo

Yes, miniflare [0] lets you run Workers locally, but I wouldn't treat it to production traffic. There's also Deno, which is very similar in technology to Workers [1]. Others are building "Workers" atop WebAssembly, and things are looking up on that front as well [2][3]. See also: https://github.com/debarshibasak/awesome-paas [0] https://github.com/cloudflare/miniflare [1] https://deno.land [2] https://github.com/suborbital/atmo [3] https://github.com/krustlet/krustlet

One of the first things we've used it for internally is to run one-off isolated tests on WebAssembly modules instead of feeding them through a production Atmo[0] instance. It basically serves as a dumb pipe for feeding data in and out of any Wasm module built for Reactr[1]. 0: https://github.com/suborbital/atmo 1: https://github.com/suborbital/reactr