Re:Time-series data: Why (and how) to use a relational datab...
by RobAtticus on Thursday April 20, 2017 @04:19PM
(#14160446)
I'm not entirely sure what you mean by event sourcing. Can you elaborate?
Re:Time-series data: Why (and how) to use a relational datab...
by cmccollough on Thursday April 20, 2017 @04:35PM
(#14160593)
It's a design pattern that's mostly relevant in the context of traditional DBs handling non-time series data - if we cut down to it, it's really about keeping a transactional DB of all events taken on the data. Microsoft seems to have some decent high-level documentation on the concept:
https://docs.microsoft.com/en-us/azure/architecture/patterns...
When talking time series, there certainly seems to be less of a use case for it in the sense that data is mostly immutable with few updates to old records, just new entries as data streams in. That being said, I wonder if there are use cases where the event sourcing concept may bring value to time series DBs - maybe I ingested some bad data that I need to go back and clean up, maybe the structure of my data changed requiring a change in my DB schema, etc. Was just curious if this is something you all have put any thought into at a high-level.
Re:Time-series data: Why (and how) to use a relational datab...
by RobAtticus on Thursday April 20, 2017 @04:56PM
(#14160788)
Not sure it's come up too often, but it's something we can think about going forward.
Do you all discuss event sourcing and how it fits within an overall TimeScaleDB strategy? Anything more than a peripheral concept?