zlacker

[parent] [thread] 5 comments
1. hughrr+(OP)[view] [source] 2021-06-12 13:54:32
I've got about 6 years operational experience with Redis. I would not use it for a queue. I struggle to consider using it as a data store these days as well with other options on the table. But that's a whole new thread so I'm not going into details here.

If you want a queue, get a queue.

If you want a relational database, get a relational database.

If you want a key-value store, get a key-value store.

Don't cross the streams.

replies(2): >>mikekl+sI >>Too+yA1
◧
2. mikekl+sI[view] [source] 2021-06-12 20:39:48
>>hughrr+(OP)
What would you use redis for, if anything?
replies(1): >>yawara+gO
◧◩
3. yawara+gO[view] [source] [discussion] 2021-06-12 21:38:52
>>mikekl+sI
I assume a key-value store.
replies(1): >>hughrr+eA1
◧◩◪
4. hughrr+eA1[view] [source] [discussion] 2021-06-13 07:39:20
>>yawara+gO
Correct
replies(1): >>mikekl+v66
◧
5. Too+yA1[view] [source] 2021-06-13 07:42:18
>>hughrr+(OP)
Not really knowing the details of Redis. What makes it a better key-value store than a Postgres table with a key-column and a value-column?
◧◩◪◨
6. mikekl+v66[view] [source] [discussion] 2021-06-14 20:37:44
>>hughrr+eA1
Perhaps I misinterpreted this part?

> I struggle to consider using it as a data store these days as well with other options on the table.

It sounds like you wouldn't use it for any purposes.

[go to top]