Timeline for How Add/Create* commands should be handled in CQRS + Event Sourcing architecture
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2, 2015 at 19:20 | answer | added | Tuukka Haapaniemi | timeline score: 14 | |
| Jul 2, 2015 at 4:14 | history | tweeted | twitter.com/#!/StackProgrammer/status/616459981236383744 | ||
| Dec 5, 2014 at 1:11 | comment | added | E.Z. Hart | Note that the Udi Dahan article you're referencing specifically calls out that his advice may not apply to event sourcing: udidahan.com/2009/06/29/dont-create-aggregate-roots/… | |
| May 6, 2014 at 2:34 | comment | added | Darien | I suspect Udi's post-title is misleading. IMHO it sounds like his real objective is that freshly-made ARs should always be reachable from some other place, in a way that captures context about why/how/who decided that the new AR needed to be created. Everything else is about how a particular implementation (NHibernate?) could make it easier to manage. | |
| Mar 18, 2014 at 16:35 | history | edited | Mequrel | CC BY-SA 3.0 | Found interesting implementation of the pattern |
| Mar 18, 2014 at 11:20 | review | First posts | |||
| Mar 18, 2014 at 11:49 | |||||
| Mar 18, 2014 at 11:02 | history | asked | Mequrel | CC BY-SA 3.0 |