Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Another aside: after going through the first two exercises I got to thinking: is there anything out there that's like "Caddy For Distributed Systems"?

By which I mean is there a framework (ideally for Go) where I could "just" implement my client-facing API and something like your Malestrom package's `Node.Handle` function but all the rest like node discovery, updates, etc is handled for me?

Or put another way: I wish there was a turn key solution to releasing an API around something like etcd or Consul, but I'm having trouble finding anything like that.

Let's say I actually wanted to deploy my own distributed version of the grow-only counter challenge, it seems like there's a lot of non-trivial operations and such I need to get right _in addition_ to my message handling logic, and that feels like a gap that if filled would allow a lot more developers to get into distributed systems development, much like how Caddy has made it order of magnitudes easier for developers to implement custom reverse proxy logic.



Isn’t based around Consul or etcd, but the encore folks https://encore.dev/docs have been building a framework that makes working with microservices much more straight forward.

I haven’t used it much, but the tool is able to generate all the code for services that want to speak to one another. This to me is enough service discovery.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: