Good article. Thanks for writing. Some questions.

Seeing your implementation of the facade layer, there is a lot of coordination logic written in there, e.g. set loading state, get entries, update them to state and to API, etc. This tells that this is not a mere facade. Probably should use a different architectural term instead. Your thoughts?

The other very important piece that I find really really really complex to figure out is the following.

For simple CRUD modues, this architecture and even many other patterns are more than enough. But complexities arise when there are going to be interactions between two "cores".

Example 1: Let's say we have another module to CRUD Fight Sequence. (Let's also assume you created another module for Villians same as for Heroes.) Now the components in the FightSequence Module must fill two dropdowns, for Heroes and Villians. How should this be structured this?

Example 2: Let's say the add/edit form component in the Villian's module must also contain a drop-down of Heroes for "Strongest Hero". How should this relationship be structured?

Would love to know your thoughts on this.