exposure-notifications-server VS mux

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/

This is not a disproval, but gorilla/mux has comparatively poor benchmark results among popular (many stars) third-party HTTP routers. , used by many users.

This attention to detail also can mean that for key abstractions in a tool or framework, what concretely goes on doesn't go unexplained. For example, when I was learning Go for web development, my first stumbling block was understanding how interfaces worked, particularly http.Handler, which is key to doing web development with Go's powerful net/http package and the fits-like-a-glove package built on top of it, the Gorilla Mux router. My way of finding out how that worked, and seeing the elegance of that interface, was pretty unorthodox - I figured out how Handlers worked by looking directly at Go's source code (which also is a demonstration of Go's readability, if you're interested in joining the Gophers!). And coming out of that was my very first tech talk at in 2015, on learning Gorilla from its Node.js counterpart, Express.js!

In this ApiGateway implementation, we've employed the Gorilla Mux router for enhanced route handling. Let's break down the key components:

Now that we have set up the Go environment, we can start building our API. The first step is to choose a framework. There are several popular frameworks for building APIs in Go, such as Gorilla mux, Echo, and Gin. For this article, we'll use Gorilla mux.

Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。

My personal favorite tools: - https://github.com/go-kit/ for building services (although it's not necessary a great tool for prototyping) - https://github.com/gorilla/mux router (although it's been recently deprecated, so I'm looking for a similar, maintained library) - https://entgo.io/ ORM - https://watermill.io/ for messaging

We will be using Gorilla Mux to create the APIs locally. Gorilla Mux implements a request router and dispatcher to match the incoming requests.