waypoint VS exposure-notifications-server

Check this out, coming in the next release: https://github.com/hashicorp/waypoint/pull/2336

As mentioned in the other comments, easy-to-read and maintainable code, high test coverage and being able to fearlessly implement new features should be a better indicator for a well-designed architecture than just bluntly implementing architectural patterns. That being said, an example for a project with a CLI and RPC server with proper architecture would be Waypoint.

I'm not really familiar with railway.app, but from reading their site it seems similar to Hashicorp's new project Waypoint, which is FOSS: https://github.com/hashicorp/waypoint

hashicorp / waypoint

Not a small one, but a real-life one, the exposure-notifications-server is usually what I like to recommend, keep in mind that you probably need a bit of Go knowledge and context before looking at it so perhaps it isn't the best introductory project to look at; however I recommend you to bookmark it for future reference.

Here, I can even link you to an article of how exposure notifications work: https://www.google.com/covid19/exposurenotifications/

Google's Exposure Notification Reference Serve is a real life example of what you're asking for.

Which is just a massive misunderstanding of how the contact tracing API works, even if you do believe that it was "surreptitiously installed ... on users [sic] phones".

https://www.google.com/covid19/exposurenotifications/ (“The Exposure Notifications System was introduced in an update to Google Play Services. This update did not automatically turn on Exposure Notifications or enable any Exposure Notifications functionality. Exposure Notifications only works if you decide to opt-in.”) Android 6.0 and above.

Source: https://www.google.com/covid19/exposurenotifications/