core VS wild-workouts-go-ddd-example

As a recap, StaticBackend is a simple backend server API easy to self-host or importable in Go program without hosting a separate server.

StaticBackend is a simple backend server API you may use to build complex web applications. Fully open source and easy to self-host. It handles lot of backend building blocks.

I want to put StaticBackend on your radar. It's an open-source backend API I've worked on for more than 3.5+ years.

I'd like to put StaticBackend - GitHub in your radar. It's a simple backend server API that tries to handle most of the common functiionalities found in web applications. It's open-source and very easy to self-host.

Since people often ask where they could contribute to a Go project, I thought I'd jump in as I took some times to create some good first contribution issues for StaticBackend.

It's not always present in issues what has to be done in a project. On that note, I'd shamelessly suggest to look at StaticBackend which is a backend API to help expedite v1 (MVP) launch time.

I can tell you what I like and don't like about my open source backend API (self-hosted Firebase) https://github.com/staticbackendhq/core

Hey, if you're interested in web backend I started StaticBackend - GitHub repo in 2019. It's a REST backend server which aim to provide most of the common building blocks like user authentication, database, file storage, websocket, schedule tasks, server-side function.

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.