remix VS wild-workouts-go-ddd-example

Also, Remix sourcemaps didn't work with Cloudflare Workers, but it seems that it should be working already. I should double-check it!

Then in this Github issue, I found something new and flashy, Paraglide JS.

Relates to https://github.com/remix-run/remix/pull/3104

The main goal of this project was to learn something new in a fun way, so I've decided to use Remix for it, and oh my - it was perfect. I was amazed by how powerful it is by using just standard web features such as cookies, query parameters, and forms. Just remember to be cautious when picking a starter template for your project. I picked the default one, and later found out it wasn't supported by Netlify. As a result, I had to delete the entire repository and start the configuration process again. 🙈

Real time data update: Remix supports Server Sent Events e.g. https://github.com/remix-run/examples/tree/main/_official-realtime-app https://github.com/remix-run/remix/discussions/2622

Sometimes the best way to learn is by looking at examples, so we’re going to walk through this Remix issue from Nick Taylor.

You don't need NextJS for SSR. There are less opinionated alternatives like Remix that was built by the React Router team and is backed by Shopify now, you can use something like Razzle or one of its alternatives for semi-opinionated pure SSR or follow the Vite Docs and just do it yourself with express.

- I've found Remix's configurable routes helps to split very large Remix projects into independent features that scales well, when multiple server output bundles drops this will scale the deployments across serverless functions also. RFC. PR.

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.