3 ms·
The argument I've always heard for this was issues with code, not the event. If for a period of time you have a bug in your code, with event sourcing, you can f
by r1cka 1y ago
The argument I've always heard for this was issues with code, not the event. If for a period of time you have a bug in your code, with event sourcing, you can fix the bug and replay all the events to correct current projections of state.
- mirekrusin 1y agoWhat if your correction renders subsequent events nonsensical?
- mrkeen 1y agoThere is a very real chance of this happening, and two choices. One - bake whatever happens into your system permanently, like 99% of all apps, and disallow corrections. Two - keep the events around so that you can check and re-check your corrections before you check in new code or data.