A Time Series Database (TSDB) is a database optimized for time-stamped or time series data. Time series are simply measurements or events that are tracked, monitored, downsampled, and aggregated over time. This could be server metrics, application performance monitoring, network data, sensor data, events, clicks, trades in a market, and many other types of analytics data. The key difference with time series data from regular data is that you’re always asking questions about it over time.
The most popular solutions today are:
- InfluxDB (★ 14,629 on GitHub, written in Go)
- Graphite (★ 4,325 on GitHub, written in Python)
- Prometheus (★ 19,717 on GitHub, written in Go)
- DalmatinerDB (★ 674 on GitHub, written in Erlang)
- Heroic by Spotify (★ 674 on GitHub, written in Java)
- Akumuli (★ 538 on GitHub, written in C++)
In addition, recently the TimescaleDB 1.0 was announced.
- TimescaleDB (★ 5,898 on GitHub, is packaged as a PostgreSQL extension). TimescaleDB is an open-source database designed to make SQL scalable for time-series data. It is engineered up from PostgreSQL, providing automatic partitioning across time and space (partitioning key), as well as full SQL support.
#tsdb #metrics #data #store
The most popular solutions today are:
- InfluxDB (★ 14,629 on GitHub, written in Go)
- Graphite (★ 4,325 on GitHub, written in Python)
- Prometheus (★ 19,717 on GitHub, written in Go)
- DalmatinerDB (★ 674 on GitHub, written in Erlang)
- Heroic by Spotify (★ 674 on GitHub, written in Java)
- Akumuli (★ 538 on GitHub, written in C++)
In addition, recently the TimescaleDB 1.0 was announced.
- TimescaleDB (★ 5,898 on GitHub, is packaged as a PostgreSQL extension). TimescaleDB is an open-source database designed to make SQL scalable for time-series data. It is engineered up from PostgreSQL, providing automatic partitioning across time and space (partitioning key), as well as full SQL support.
#tsdb #metrics #data #store
IronDB (★ 854) - is a relentless key-value store for the browser.
IronDB is the best way to store persistent key-value data in the browser. Data saved to IronDB is redundantly stored in Cookies, IndexedDB, LocalStorage, and SessionStorage, and relentlessly self heals if any data therein is deleted or corrupted.
For example, clearing cookies is a common user action, even for relatively non-technical users. And browsers will unceremoniously delete IndexedDB, LocalStorage, and/or SessionStorage without warning.
IronDB is resilient in the face of such events.
#js #keyvalue #store #storage #resilient
IronDB is the best way to store persistent key-value data in the browser. Data saved to IronDB is redundantly stored in Cookies, IndexedDB, LocalStorage, and SessionStorage, and relentlessly self heals if any data therein is deleted or corrupted.
For example, clearing cookies is a common user action, even for relatively non-technical users. And browsers will unceremoniously delete IndexedDB, LocalStorage, and/or SessionStorage without warning.
IronDB is resilient in the face of such events.
#js #keyvalue #store #storage #resilient
KeyDB - (★2,8k at GitHub) is a high performance fork of Redis with a focus on multithreading, memory efficiency, and high throughput. In addition to multithreading, KeyDB also has features only available in Redis Enterprise such as Active Replication, FLASH storage support, and some not available at all such as direct backup to AWS S3.
KeyDB maintains full compatibility with the Redis protocol, modules, and scripts. This includes the atomicity gurantees for scripts and transactions. Because KeyDB keeps in sync with Redis development KeyDB is a superset of Redis functionality, making KeyDB a drop in replacement for existing Redis deployments.
On the same hardware KeyDB can perform twice as many queries per second as Redis, with 60% lower latency. Active-Replication simplifies hot-spare failover allowing you to easily distribute writes over replicas and use simple TCP based load balancing/failover. KeyDB's higher performance allows you to do more on less hardware which reduces operation costs and complexity.
#redis #kv #store #bobukrecommends
KeyDB maintains full compatibility with the Redis protocol, modules, and scripts. This includes the atomicity gurantees for scripts and transactions. Because KeyDB keeps in sync with Redis development KeyDB is a superset of Redis functionality, making KeyDB a drop in replacement for existing Redis deployments.
On the same hardware KeyDB can perform twice as many queries per second as Redis, with 60% lower latency. Active-Replication simplifies hot-spare failover allowing you to easily distribute writes over replicas and use simple TCP based load balancing/failover. KeyDB's higher performance allows you to do more on less hardware which reduces operation costs and complexity.
#redis #kv #store #bobukrecommends
