←back to thread

The Fastest Redis Ever

(redis.io)
82 points lsferreira42 | 1 comments | 18 Nov 24 21:39 UTC | HN request time: 0s | source
Show context
pcthrowaway ◴[21 Nov 24 07:19 UTC] No.42201918[source]▶
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.

replies(2): >>42202211 #>>42207333 #
jeltz ◴[21 Nov 24 08:21 UTC] No.42202211[source]▶
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?
replies(1): >>42202223 #
rcarmo ◴[21 Nov 24 08:24 UTC] No.42202223[source]▶
Likely when it's small enough to keep in RAM and you want to do some sort of on-the fly aggregation/correlation.
replies(1): >>42202269 #
jeltz ◴[21 Nov 24 08:31 UTC] No.42202269[source]▶
Then you can usually just store it in the memory of your application. No need to complicate your stack by running another service.
replies(5): >>42202304 #>>42202310 #>>42202952 #>>42205750 #>>42208946 #
jeremycarter ◴[21 Nov 24 10:43 UTC] No.42202952[source]▶
Some large IoT systems need ephemeral timeseries.
replies(1): >>42203612 #
1. jeltz ◴[21 Nov 24 12:22 UTC] No.42203612{3}[source]▶
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.