Timeline for Decoupling modules of a monolith
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 31, 2023 at 6:15 | vote | accept | Andy Cox | ||
| Mar 30, 2023 at 15:03 | comment | added | pjc50 | Cross-microservice transactions are almost impossible to do well, so in going to microservices you tend to give up referential integrity. But you gain loose development coupling, as you say. | |
| Mar 30, 2023 at 14:44 | comment | added | Andy Cox | That's a great answer. I guess I'd use an Integration Event to signal when a module deletes an entity so that the CMS can delete the PageNodeReference entity. Loss of referential integrity might be a good trade-off for the loose coupling. | |
| Mar 30, 2023 at 8:01 | history | edited | Doc Brown | CC BY-SA 4.0 |
deleted 1 character in body
|
| Mar 29, 2023 at 20:05 | history | answered | Doc Brown | CC BY-SA 4.0 |