Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Redis 8.8: New array data structure, rate limiter, performance improvements

redis.io

Post reply on HN
Print view View original

111–118 of 118 posts

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#111

Post by stingraycharles »

atmosx wrote: post #89
freakynit wrote: post #35

Earlier quoted context omitted.

Language's own native data-structures are generally much more capable and vast. 99%+ developers use only a very limited set of those capabilities. This approach packages those most used ones into a nice, consistent DSL. It's similar in effect to what busybox does to shell utilities, though the motives are different.

Doesn’t depend on the language? Actually I am thinking of the standard library… Python’s in kinda huge and some are hard (for me) to grasp. Golangs seem pretty simple.

Language’s own native data structures isn’t limited to just the standard library.

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#112

Post by 0x457 »

simonw wrote: post #78
0x457 wrote: post #69

Earlier quoted context omitted.

Can you name a single language that can talk to redis and doesn't have these in a form of a library that integrates with an app better than mystical embedded redis? Every language you can talk to redis most likely has a library to do that, and it probably works much better with the rest of application than "embedded redis". If it doesn't, it probably has C-FFI and there is "fast, robust and well understood" implement…

Sure. But if Redis was embeddable you'd get a robust C-FFI style implementation of those data structures which has been tested a lot more than some random library that has almost no existing users or active maintenance. (I'm not personally sold on embedded Redis myself, but the question was "Aren’t your own programming language’s constructs much more well-defined / understood?")

> you'd get a robust C-FFI style implementation of those data structures which has been tested a lot more than some random library that has almost no existing users or active maintenance.

What are these mystical random libraries you're talking about? There is a solid C implementation of every data structure on this planet.

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#113

Post by 0x457 »

jchw wrote: post #68
0x457 wrote: post #67

Earlier quoted context omitted.

Well, if you have a single instance than using language libraries and structures will be better in most cases. If you use multiple nodes, then you probably want your redis lifecycle not be tied to application lifecycle.

I am not aware of an in-process alternative similar to what Redis offers.

I would Cache with TTL? A cache that can store lists?

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#114

Post by anapeksha »

9dev wrote: post #3

While 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…

[dead]

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#115

Post by simonw »

0x457 wrote: post #112
simonw wrote: post #78

Earlier quoted context omitted.

Sure. But if Redis was embeddable you'd get a robust C-FFI style implementation of those data structures which has been tested a lot more than some random library that has almost no existing users or active maintenance. (I'm not personally sold on embedded Redis myself, but the question was "Aren’t your own programming language’s constructs much more well-defined / understood?")

> you'd get a robust C-FFI style implementation of those data structures which has been tested a lot more than some random library that has almost no existing users or active maintenance. What are these mystical random libraries you're talking about? There is a solid C implementation of every data structure on this planet.

Show me a better C library for HyperLogLog than the one baked into Redis.

I went looking and the pure C ones all appeared to be untouched in 10+ years - https://github.com/ivitjuk/libhll and https://github.com/avz/hll for example.

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#116

Post by [deleted] »

lukaslalinsky wrote: post #33
tapoxi wrote: post #7

Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?

I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.

[deleted]

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#117

Post by 0x457 »

simonw wrote: post #115
0x457 wrote: post #112

Earlier quoted context omitted.

> you'd get a robust C-FFI style implementation of those data structures which has been tested a lot more than some random library that has almost no existing users or active maintenance. What are these mystical random libraries you're talking about? There is a solid C implementation of every data structure on this planet.

Show me a better C library for HyperLogLog than the one baked into Redis. I went looking and the pure C ones all appeared to be untouched in 10+ years - https://github.com/ivitjuk/libhll and https://github.com/avz/hll for example.

Why? You can just adapt/use https://github.com/redis/redis/blob/unstable/src/hyperloglog...

Why does it need to be pure C? There are C++ implementations. It's an algorithm not a social media app, it doesn't need to be updated once a week, C also not node.js - it doesn't break compatibility every release. What is wrong with these 10+ years touched ones?

Even the redis version of HLL isn't updated all that often.

Re: Redis 8.8: New array data structure, rate limiter, performance improvements

#118

Post by simonw »

0x457 wrote: post #117
simonw wrote: post #115

Earlier quoted context omitted.

Show me a better C library for HyperLogLog than the one baked into Redis. I went looking and the pure C ones all appeared to be untouched in 10+ years - https://github.com/ivitjuk/libhll and https://github.com/avz/hll for example.

Why? You can just adapt/use https://github.com/redis/redis/blob/unstable/src/hyperloglog... Why does it need to be pure C? There are C++ implementations. It's an algorithm not a social media app, it doesn't need to be updated once a week, C also not node.js - it doesn't break compatibility every release. What is wrong with these 10+ years touched ones? Even the redis version of HLL isn't updated all that often.

That's exactly what I'm arguing for here: it would be useful if Redis data structures like that were available to be easily embedded in other programs.

"You can just adapt X from Redis" is the whole point of this hypothetical.

Post reply on HN