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.…
Gotcha. This may be a bit of a tangent to my above question but it came to mind from the topic of transitioning: Do you all discuss event sourcing and how it fits within an overall TimeScaleDB strategy? Anything more…
What might the transition out of a Cassandra-based tech stack look like if I wanted to go relational?
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.…
Gotcha. This may be a bit of a tangent to my above question but it came to mind from the topic of transitioning: Do you all discuss event sourcing and how it fits within an overall TimeScaleDB strategy? Anything more…
What might the transition out of a Cassandra-based tech stack look like if I wanted to go relational?