4 ms·
Is this open source? How does it differ from TimescaleDB or InfluxDB?
by polskibus 6y ago
Is this open source? How does it differ from TimescaleDB or InfluxDB?
- redis_mlc 6y agoMetricsDB appears to be HDFS-based. TimescaleDB is Postgres-based and InfluxDB is memory and log-based. Prometheus is file-based.
- sytse 6y agoThanks for this clear summary of the differences.
- squarecog 6y agoWhile HDFS is indeed used for exporting old data and storing some partition mapping metadata, it's clear from the blog post that MetricsDB is much more reliant on BlobStore as well as MetricsDB-specific services. > The servers checkpoint in-memory data every two hours to durable storage, Blobstore. We are using Blobstore as durable storage so that our process can be run on our shared compute platform with lower management overhead.
- risyachka 6y agoAs fas as I have seen, 99% of in-house solutions are tailored for exactly 1 use case - the company that built it. Existing solutions like InfluxDB are made way more generic. Companies like Twitter, Uber etc can spend many millions and won't notice so they can build tailored databases for themselves. Will someone else use it? Probably not (sure unless this is something new or that differs a lot from existing solutions and gives a lot of benefits)
- privateprofile 6y agoI think it has (sadly) become common for people/companies to adopt software just/mostly because it came from Twitter/FAANG or whatever company that is high on hype...
- akulkarni 6y agoAlso, TimescaleDB is a general purpose time-series database, which means that it not only works for metrics data, but also many other datatypes (strings, arrays, JSON, etc). You can also create indexes on any of these fields. Because TimescaleDB is built on Postgres, it is also a relational time-series database. Ie you can store metadata / business data alongside your time-series data. (Note: I work on TimescaleDB.)