3 ms·
The "why should I care" is about 3/4 of the way down the page: > None of these numbers are exact, but the structural gap is clear: a handful of nodes costing r
by mdwaud 6mo ago
The "why should I care" is about 3/4 of the way down the page:
> None of these numbers are exact, but the structural gap is clear: a handful of nodes costing roughly $560/month versus $10,000-20,000/month for a managed service at the same scale. As we explained earlier, it’s practical to operate OpenData Timeseries yourself and fully realize these massive cost savings since it isn’t a traditional distributed database that manages partitioned and replicated state.
It doesn't look 100% turn-key, but those are compelling numbers.
- agavra 6mo agoGood point, a tl;dr is probably worthwhile. It's definitely not quite turn key just yet but we've been dogfooding it in production against a moderate metrics use case (~30k samples/s) and have it hooked up to grafana (you just configure a prometheus source and point to your deployed URL). We run it on a single node with no replicas ;)
- apurvamehta 6mo agoGood call out, updated the intro with a summary of the cost benefit. Thanks for the feedback!