3 ms·
> For a start, you're going to have to define your schema. Does one tree have one row or is it one case has one row? It seems to me you're defining a schema re
by picardo 5y ago
> For a start, you're going to have to define your schema. Does one tree have one row or is it one case has one row?
It seems to me you're defining a schema regardless, but with event sourcing your schema is embedded in your events rather than your database. And you're putting off the reconciliation to projection phase. I get it. But you still need to worry about writing transformations for your data to bring it up to date with your latest schema... That is often the most frustrating part.
- adamauckland 5y agoYeah, exactly right, we found it was a few iterations before we had the Base Event Schema defined with enough data for every event. Of course, with all these articles they miss out that you're not supposed to just do Event Sourcing, it's one part of the system, like we mix RDS and object stores depending on the right purpose.