TimescaleDB
InfluxData
Prometheus
OpenTSDB
RRDTool
VictoriaMetrics
QuestDB
Redis
Tile38
VoltDB
Redis
Aerospike
Beringei
BuntDB
Hazelcast
Algolia
TimescaleDB Tile38Based on our record, TimescaleDB should be more popular than Tile38. It has been mentiond 5 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
(:alert: I work for Timescale :alert:) It's funny, we hear this more and more "we did some research and landed on Influx and ... Help it's confusing". We actually wrote an article about what we think, you can find it here: https://www.timescale.com/blog/what-influxdb-got-wrong/ As the QuestDB folks mentioned if you want a drop in replacement for Influx then they would be an option, it kinda sounds that's not what... - Source: Hacker News / 6 months ago
If you like PostgreSQL, I'd recommend starting with that. Additionally, you can try TimescaleDB (it's a PostgreSQL extension for time-series data with full SQL support) it has many features that are useful even on a small-scale, things like:. Source: over 1 year ago
I have built a Django server which serves up the JSON configuration, and I'd also like the server to store and render sensor graphs & event data for my Thing. In future, I'd probably use something like timescale.com as it is a database suited for this application. However right now I only have a handful of devices, and don't want to spend a lot of time configuring my back end when the Thing is my focus. So I'm... Source: over 2 years ago
I've seen a lot of benchmark results on timescale on the web but they all come from timescale.com so I just want to ask if those are accurate. Source: over 2 years ago
Ryan from Timescale here. We (TimescaleDB) just launched the second annual State of PostgreSQL survey, which asks developers across the globe about themselves, how they use PostgreSQL, their experiences with the community, and more. Source: about 3 years ago
I actually worked on a project that did this. We used a database called "Tile38" [1] which used an R-Tree to make geospatial queries speedy. It was pretty good. Our dataset was ~150 GiB, I think? All in RAM. Took a while to start the server, as it all came off disk. Could have been faster. (It borrowed Redis's query language, and its storage was just "store the commands the recreate the DB, literally", IIRC. Dead... - Source: Hacker News / almost 2 years ago
InfluxData - Scalable datastore for metrics, events, and real-time analytics.
VoltDB - In-memory relational DBMS capable of supporting millions of database operations per second
Prometheus - An open-source systems monitoring and alerting toolkit.
Redis - Redis is an open source in-memory data structure project implementing a distributed, in-memory key-value database with optional durability.
OpenTSDB - OpenTSDB is a distributed, scalable Time Series Database (TSDB) written on top of HBase.
Aerospike - Aerospike is a high-performing NoSQL database supporting high transaction volumes with low latency.
