Keynote: Event sourcing - Greg Young - DPC2016

>That's pretty much right in the name. Are you storing documents? Probably a document store. Are you storing graphs? Try a graph store. Are you storing objects that are related to other objects? A relational store would be a good bet. Understanding the underlying math of each of the systems is the easiest way to understand which storage model to use. Just guessing out of ignorance is a bad way to do it. I'd argue that it's not quite so simple. Many people choose to store documents in relational databases because they care about the querying requirements of the metadata for said documents. Some will choose document storage first because it fits the requirements of their project to begin with…

…keep updating a projection of the current state of everything in a relational database for easy querying. It's a very expansive subject, and once you start getting into it, it makes you think about your data quite differently. There's a guy called Greg Young who has done a lot of excellent talks on the subject of event sourcing; and here's one: [video Mind you, it's also one of those topics where you now have a new hammer in your toolbox, and every problem starts looking like a nail.…