wtf VS wild-workouts-go-ddd-example

I am new to go. Found wtf dial - ( https://github.com/benbjohnson/wtf ) while looking to get some project based learning. This looks pretty interesting but when I did git clone of the project my vs code is giving number dependency related problems like below.

There are a few Go projects meant to be learned from:

- https://github.com/pion/opus for to learn audio

- https://github.com/benbjohnson/wtf for overall production quality

- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors

I read about https://github.com/benbjohnson/wtf and the connected blog here a couple of times. Seems quite good.

Personally I think the method is the layered architecture approach. Example: https://github.com/benbjohnson/wtf

Take a look at the discussions in the repo: https://github.com/benbjohnson/wtf/discussions

https://github.com/benbjohnson/wtf This repo serves as an example and fits Go very well in my opinion. Check the discussions on the repo and the blog posts.

ThreeDotsLabs/wild-workouts-go-ddd-example — Clean Architecture + CQRS in Go, with a blog series explaining every decision.

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 .