go-rabbitmq VS pkgsite

go-rabbitmq

I maintain this open-source project for RabbitMQ. I've used it in very large production systems, might be of use to you.

Try this one: https://github.com/wagslane/go-rabbitmq

Reading the standard library will give you ideas/insight about various Go idiomatic patterns/approaches, and you can see a full website/API implementation in the pkg.go.dev repository (https://github.com/golang/pkgsite). Projects like https://github.com/etcd-io/etcd may be interesting too.

Let's look at some real codebase for an example on how to write database tests without mocking. The source code for the Go package discovery site(https://pkg.go.dev/) is available at[1] That site uses postgres as its primary database[2]. The database package has a method called GetLatestInfo[3] that fetches the latest versions of a module. That method is called from the frontend http handlers[4] via an interface[5] When it comes to testing that frontend handler, you would expect the tests to use a mock implementation of that interface method. But that's not what they do, instead they use a real postgres database in the test[6].

The code behind pkg.go.dev is also open-source and might be an interesting read.

BTW, the number of dependencies of pkgsite surprises me: https://github.com/golang/pkgsite/blob/master/go.mod

The source for Go's pkg site has been helpful to me https://github.com/golang/pkgsite

In my unpopular opinion, the go net/http is good enough to develop the web http application. The standard API is clean and well-documented. One of example is the pkgsite (https://github.com/golang/pkgsite).

It's also available as a mirror at https://github.com/golang/pkgsite. All the golang.org/x/* packages are thankfully available there, making them pretty easy to find.