3 ms·

The inclusion of Redis timeseries is huge! This was available for a long time as an extension as part of Redis Stack, but most hosted Redis providers don't mak

The inclusion of Redis timeseries is huge! This was available for a long time as an extension as part of Redis Stack, but most hosted Redis providers don't make extensions available (I'm assuming due to nuances in Redis's not-quite-open licensing). If cloud providers which include Redis are now going to include this, it opens up a lot of potential for my use case.

jeltz 2y ago
When do you want to store your time series data in Redis and not a database like TimescaleDB or Clickhouse which is optimized for storage on disk and analytics queries?
- rcarmo 2y ago
  Likely when it's small enough to keep in RAM and you want to do some sort of on-the fly aggregation/correlation.
  - jeltz 2y ago
    Then you can usually just store it in the memory of your application. No need to complicate your stack by running another service.
    - _joel 2y ago
      Isn't this just RocksDB?
      - vrnvu 2y ago
        Or DuckDB
    - rizky05 2y ago
      [dead]
    - jeremycarter 2y ago
      Some large IoT systems need ephemeral timeseries.
      - jeltz 2y ago
        Which you can store just fine in-memory in a normal data structure. And if you need advanced query capabilities or a query planner there is DuckDB. Using Redis seems like you get most of the disadvantages of having to run a whole database with few of the advantages.
    - pcthrowaway 2y ago
      When you need to be able to retrieve the timeseries data for some period of time, storing it in the application memory doesn't really work since the application will restart whenever updates are made. Also, redis timeseries offers the ability to downsample to some defined period which is really handy (and afaik isn't really provided by other timeseries databases) as well as set a retention policy.
    - rcarmo 2y ago
      your application can consist of multiple processes.
reconditerose 2y ago
It was always, and still is, a license issue. Redis stack had a proprietary license and now Redis has a proprietary license.

jeltz 2y ago

When do you want to store your time series data in Redis and not a database like TimescaleDB or Clickhouse which is optimized for storage on disk and analytics queries?

rcarmo 2y ago
Likely when it's small enough to keep in RAM and you want to do some sort of on-the fly aggregation/correlation.
- jeltz 2y ago
  Then you can usually just store it in the memory of your application. No need to complicate your stack by running another service.
  - _joel 2y ago
    Isn't this just RocksDB?
    - vrnvu 2y ago
      Or DuckDB
  - rizky05 2y ago
    [dead]
  - jeremycarter 2y ago
    Some large IoT systems need ephemeral timeseries.
    - jeltz 2y ago
      Which you can store just fine in-memory in a normal data structure. And if you need advanced query capabilities or a query planner there is DuckDB. Using Redis seems like you get most of the disadvantages of having to run a whole database with few of the advantages.
  - pcthrowaway 2y ago
    When you need to be able to retrieve the timeseries data for some period of time, storing it in the application memory doesn't really work since the application will restart whenever updates are made. Also, redis timeseries offers the ability to downsample to some defined period which is really handy (and afaik isn't really provided by other timeseries databases) as well as set a retention policy.
  - rcarmo 2y ago
    your application can consist of multiple processes.

reconditerose 2y ago

It was always, and still is, a license issue. Redis stack had a proprietary license and now Redis has a proprietary license.