vuex-orm VS modular-monolith-with-ddd

You're absolutely right. I should have mentionned that the app uses Vuex-ORM to handle and query the data. The actual building of the reports contains various calculations and is done off the main thread. The reports are then saved as a model in vuex-orm, this basicaly acts as a cache. The thing is I don't know when to invalidate the cache or not so everything is invalidated when a new data event is added. There's nothing reactive about it.

Most people try to have front-end state be a 1-1 mapping of the DB. One of the easiest way about it is to use a front-end "ORM" like vuex-orm.

Not quite the same but Vuex ORM does a few of these things. Main similarity is helping to abstract your API calls out of each individual component. https://vuex-orm.org/

Most interactions with the store are done with VuexOrm, which gives us a gorgeous API. Stuff like this:

In one lib: Vuex-Orm

Thanks for great comment! I have one question.

The biggest thing I miss in react ecosystem is decent redux ORM. https://vuex-orm.org is just so great for so many use cases (agree that it might an antipattern in many situations). Is there any chance that https://github.com/redux-orm/redux-orm, which was actually what inspired vuex-orm, would get more love from anyone to become an actively maintained library?

Thanks

I know there is a package for persisting Vuex data via the local store but wondered if anyone knows this works with Vuex ORM.

Sounds like you need this: https://vuex-orm.org/

could peep this https://github.com/vuex-orm/vuex-orm

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!