infra VS mux

Check out https://infrahq.com. I saw the founder give a talk at the Civo conference in Feb.

using generics you can even include request and response structs in your handlers. i did that here https://github.com/infrahq/infra/blob/main/internal/server/routes.go

infra

You should try Infra. It works with any flavor of Kube and can hook up Okta, Google, and AD (and anything that supports OpenID Connect). It can pull in your cluster/roles, and set up the cluster/role bindings. It's open source, although there is also a SaaS version if you don't want to self host.

I use them frequently. see https://github.com/infrahq/infra/blob/main/internal/server/routes.go

Github repo: https://github.com/infrahq/infra

if you like Go and backend/infrastructure you might like https://github.com/infrahq/infra. it’s simple identity and access management for kubernetes (and eventually others).

not sure what you’re talking about. we use generics extensively and love it. https://github.com/infrahq/infra

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.