Timeline for Modelling invariants over different aggregates
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2024 at 18:22 | comment | added | Christophe | @DocBrown I edited to re-clarify and also say a word about the saga pattern principle. I leave you the exclusivity of eventual consistency. | |
| Jun 3, 2024 at 18:18 | history | edited | Christophe | CC BY-SA 4.0 | added 193 characters in body |
| Jun 3, 2024 at 17:41 | comment | added | Christophe | @DocBrown This is indeed the case of the saga pattern and described in the link. i mentioned it in an earlier version but it got lost in the simplification edits. It's still there implicitly, since the alternative solution to the saga is said toi avoid temporary mismatch, which contains the claim by contraposition ;-) | |
| Jun 3, 2024 at 14:51 | comment | added | Doc Brown | I think you forgot to mention one simple alternative for dealing with the business rule / invariant: allowing the rule to be broken temporarily (a.k.a "eventual consistency"). That avoids the need for the Saga pattern, does not require Domain events and avoids Food objects having to know about the meals. | |
| Jun 2, 2024 at 13:56 | history | edited | Christophe | CC BY-SA 4.0 | added 194 characters in body |
| Jun 2, 2024 at 13:30 | history | edited | Christophe | CC BY-SA 4.0 | added 268 characters in body |
| Jun 2, 2024 at 11:05 | history | answered | Christophe | CC BY-SA 4.0 |