go-clean-arch VS wild-workouts-go-ddd-example

I'm working on a project that makes use of Hexagonal Architecture to keep things loosely coupled and I learned golang recently. So, I would recommend you to check out Go clean arch, I think you can a learn a lot from it.

Try this

It will be good to have a look at the Go (Golang) Clean Architecture based on Uncle Bob's Clean Architecture https://github.com/bxcodec/go-clean-arch

Has anyone come across any Golang repo like go-clean-arch which uses elasticsearch? As I am a beginner and wanted to have a bit of practice of building microservice using Go with Elasticsearch.

Thanks, everyone. I am able to understand a few things using go-elasticsearch. Though Olivere/elastic is simpler, it is not future-proof. I just wanted a repository similar to cleanarchitecture which uses elasticsearch, on the top of which I can practice. Please provide a link here if anyone has come across such a repo.

View on GitHub

https://threedots.tech/post/introducing-clean-architecture/ https://github.com/bxcodec/go-clean-arch

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.