Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?
Redis 8.8: New array data structure, rate limiter, performance improvements
11–20 of 118 posts
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#12Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#13While I love Redis as a versatile tool for external data structures, it's still lacking in two areas IMHO: One, it would be cool to be able to embed it, similar to sqlite, directly into applications. Two, the HA story is so much more complicated than it should be. I totally acknowledge that concurrency and distributed computing is hard, but it should not require reading heaps of documentation and understanding two en…
I'm asking as a non-webdev who never quite got what Redis actually does, but would love to learn.
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#14While I love Redis as a versatile tool for external data structures, it's still lacking in two areas IMHO: One, it would be cool to be able to embed it, similar to sqlite, directly into applications. Two, the HA story is so much more complicated than it should be. I totally acknowledge that concurrency and distributed computing is hard, but it should not require reading heaps of documentation and understanding two en…
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#15Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#16While I love Redis as a versatile tool for external data structures, it's still lacking in two areas IMHO: One, it would be cool to be able to embed it, similar to sqlite, directly into applications. Two, the HA story is so much more complicated than it should be. I totally acknowledge that concurrency and distributed computing is hard, but it should not require reading heaps of documentation and understanding two en…
What would be the point of embedding Redis into an application? What's the advantage of using Redis over using the builtin (or third party) data structures of the language the application is developed in? I'm asking as a non-webdev who never quite got what Redis actually does, but would love to learn.
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#17Earlier quoted context omitted.
Genuinely interested why we need HA in redis, just not read round robin from multiple non-HA instances? Redis (and memcache) are memory caches and should be treated like that, not like highly consistent distributed session store.
Redis doesn't necessarily have to be used as a cache. Streams, for example, make it a great message queue; but a single-node message queue is a single point of failure and thus not viable for many setups.
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#18Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#19Earlier quoted context omitted.
What would be the point of embedding Redis into an application? What's the advantage of using Redis over using the builtin (or third party) data structures of the language the application is developed in? I'm asking as a non-webdev who never quite got what Redis actually does, but would love to learn.
For simple cases, it is probably a total overkill to even consider it, but for something heavier, embedding the database gives you a chance to trivially migrate later to a separate database server.
Re: Redis 8.8: New array data structure, rate limiter, performance improvements
#20While I love Redis as a versatile tool for external data structures, it's still lacking in two areas IMHO: One, it would be cool to be able to embed it, similar to sqlite, directly into applications. Two, the HA story is so much more complicated than it should be. I totally acknowledge that concurrency and distributed computing is hard, but it should not require reading heaps of documentation and understanding two en…
What would be the point of embedding Redis into an application? What's the advantage of using Redis over using the builtin (or third party) data structures of the language the application is developed in? I'm asking as a non-webdev who never quite got what Redis actually does, but would love to learn.