Timeline for Event sourcing, replaying and versioning
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 5, 2020 at 18:00 | history | tweeted | twitter.com/StackSoftEng/status/1268965816634159113 | ||
| Feb 17, 2016 at 14:39 | vote | accept | Antony Woods | ||
| Feb 17, 2016 at 13:33 | answer | added | theMayer | timeline score: 21 | |
| Feb 16, 2016 at 14:35 | history | edited | Antony Woods | CC BY-SA 3.0 | added 1381 characters in body |
| Feb 16, 2016 at 14:03 | comment | added | Antony Woods | @rmayer06 I think an example is what I'm after! | |
| Feb 15, 2016 at 21:32 | comment | added | Songo | Maybe Event upcasting can solve your problem: blog.trifork.com/2012/04/17/… | |
| Feb 15, 2016 at 18:49 | comment | added | theMayer | The question seems to mix a couple of concerns. Event sourcing is an architectural strategy to deal with systems where a lot of changes to the underlying data are taking place. Versioning of DTOs and backups and data is another matter altogether. Event sourcing is not specifically designed to get you bare-metal restore capability - for that, you need to have a specific strategy in place. | |
| Feb 15, 2016 at 18:24 | answer | added | VoiceOfUnreason | timeline score: 5 | |
| Feb 15, 2016 at 17:50 | history | asked | Antony Woods | CC BY-SA 3.0 |