Buffalo VS mux

You should probably stop because this is not a Go-way. And you wan't find anything with "batteries" other than https://github.com/gobuffalo/buffalo and https://github.com/beego/beego

Haven't see anyone actually using them in production though.

No default. There is Buffalo which is modeled after Rails, haven't used it in anger though.

https://gobuffalo.io

In general, no. But if you do seek for one, I think https://gobuffalo.io is very good.

There is https://gobuffalo.io/ and there is https://github.com/livebud/bud. Both are interesting approaches, but sadly, without real business interest from the community. See, 90% of what makes Laravel Laravel (or Rails Rails) is business adoption. And, as you will sadly find out, the business adoption for traditional Web applications is exactly zero. If you don't want to make the same mistake as I did, and spend 3 years of your life searching for it, do as the others advised - just use the tools and frameworks that have already been built to solve the problem you need.

If you like Ruby on Rails, there is Buffalo.

Buffalo is currently built on Gorilla which complicates building a business on it right now as Gorilla has shifted to public archive since it has no maintainer. https://github.com/gobuffalo/buffalo/issues/2360

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.

FYI, Gorilla Mux has been archived. It’s easy to write this without it.