rebel-northwind VS modular-monolith-with-ddd

you can check mine https://github.com/NobodyButMe-Haiya/rebel-northwind . Good luck v2 still on development

source code - https://github.com/NobodyButMe-Haiya/rebel-northwind

We got example but not sure how dto thing and don't prefer to .https://github.com/NobodyButMe-Haiya/rebel-northwind

https://github.com/NobodyButMe-Haiya/rebel-northwind/blob/master/RebelCmsTemplate/Views/Home/Main.cshtml and can view the output in youtube.

that mostly using ef and linq . You can also return sql result into object and filter via linq . You can check my example in github https://github.com/NobodyButMe-Haiya/rebel-northwind/blob/master/RebelCmsTemplate/Repository/Setting/ProductCategoryRepository.cs . We also return as object and if you want to use linq okay also . Just think as mostly if you using x/id you can get the findById style but if y/search you filter data wildcard . It depend on how you want the result as html page or json value.** sorry if this confuse for beginner.

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!