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 packa

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/bus/README.md 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?