modular-monolith-with-ddd VS awesome

Link to PR here: https://github.com/kgrzybek/modular-monolith-with-ddd/pull/286

- https://github.com/kgrzybek/modular-monolith-with-ddd (a really well documented example)

You can see there is a module called building_blocks. Inside it, I keep all the utilities needed in the project, like a logger, serializers, and so on. I did not make up this name, I borrowed it from this repo.

9. Modular Monolith with TDD

This covers far more than just DDD, however, I find the links and README super helpful for a wide range of subjects: https://github.com/kgrzybek/modular-monolith-with-ddd

Modular monolith. Here is one of the best production-ready examples https://github.com/kgrzybek/modular-monolith-with-ddd

Am wondering what react community thinks of DDD.

I've been reading "blue" DDD book (by Eric Evans) and "red" book (by Vaugh Vernon) and that was a completely "my whole life was a lie" type of experience and relief at the same time. It's just so great to have the principles of who to structure the code. It, by definition makes, your codebase structure meaningful. Because it's structured according to some common knowledge, not your random thoughts at the time you were writing code.

I was surprised to find so little DDD react sample codebases. Let's say for backend there is huge amount of samples, i.e. https://github.com/kgrzybek/modular-monolith-with-ddd . For react/frontend I have bookmarked only https://github.com/talyssonoc/react-redux-ddd/tree/master/sr... and few more, but those others does not meet the optional criteria i like really much - at the highest (or at app) level all codebase need to have folders app, domain, infra and ui. Simple rule, but simplifies life a lot.

So my question is - is DDD for some reasons not very applicable for app frontend development. Or it just never became popular. Or maybe DDD is popular amongst react developers, just I am not aware of this.

Many thanks for any ideas and comments!

In the days before "google it" was a synonym for "find it", we had different curated link sites, and even pyhsical magazines with hand-curated lists of links that people interested in a certain topic might find interesting. This still exists today in some forms, for example the "awesome lists" that you see for some programming topics, for example https://github.com/sindresorhus/awesome .

Just like there was a time when 90%-99% of all email traffic was viagra spam, I imagine in the future most of the internet by volume will be AI-generated trash, and those in the know will still circulate lists of where the other 1% can be found.

An even brighter scenario is that someone, maybe a kid tinkering in their garage, figures out how to make a search engine that finds the good stuff, doesn't immediately die to AI bot farms' SEO efforts, and is financially viable.

2. Awesome Lists

Software Engineering Blogs

He appears to be the original creator of the “Awesome X” repo: https://github.com/sindresorhus/awesome

Awesome React

I'm just going to leave this here: awesome git repo

You don't need any particular requirement to consult issues section on GitHub. If you need a place to follow along this post, my chosen repository for today's blog post is Awesome.

I have an awesome list GitHub repository that needs a few icons & a banner made. I was wondering if any students in graphic design would be willing to commission a few for me? I'm willing to pay either hourly, or by the project and can pay cash or venmo. Note that the art will end up as CC0, so you'd essentially be waiving any right to the artwork.

yah, come to think of it in the curated space, this reminds me of that awesome X family of github pages. Looks like someone compiled a bunch of them here https://github.com/sindresorhus/awesome#databases. I have found those to be highly valuable treasure troves pregnant with rich and relevant information.

10. Awesome