wild-workouts-go-ddd-example VS pkgsite

Take a look at: https://github.com/ThreeDotsLabs/wild-workouts-go-ddd-exampl...

(I’m one of the authors.)

This project shows how to apply more complex patterns popular in business applications while staying true to the Go ideas, and not copying them blindly from Java.

In the Go community, you’ll often hear people say „just keep things simple” beats all patterns and is all you need. This may be true if you write a CLI tool or a small library, but if you have a team maintaining a big application, some patterns are super helpful.

Here is a reference implementation by the same authors of the blog post you referenced: https://github.com/ThreeDotsLabs/wild-workouts-go-ddd-example/tree/master/internal/trainer.

In this case I recommend Three Dots Labs blog and Ardan Labs courses and blog posts.

As a rather new developer, I'm ashamed to admit that I struggle with this. I've seen the Dave Cheney writeup about it and I agree with your reasoning, but sometimes I end up in situations like this, where they wrote a server utility, put it into the common package and imported it into the services that need it. The issue I have is the organization of it all because the folder structure seems to make a clear separation of the core services from the utility package. If you have any ideas or tips to help avoid it, that'd be awesome!

Clean architecture is not tied to some specific paradigm. It's a way of thinking about programs that is common to almost every mature developer. Many developers use it without even knowing the name - they just came to it by themselves through many tries and errors. There is a good free book about using it in Go, called Go with the Domain if you interested.

Wild Workouts should match your needs: https://github.com/ThreeDotsLabs/wild-workouts-go-ddd-example

For Event-Driven / DDD / Microservice projects, take a look at this Github org https://github.com/ThreeDotsLabs and their blog detailing the techniques used https://threedots.tech .

Nice job at taking a stab at DDD in Go! You may want to check out https://github.com/ThreeDotsLabs/wild-workouts-go-ddd-example for some inspiration and learning around DDD and Go.

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.