Live data from Hacker News

The End of the Redis Adventure

antirez.com

31–40 of 308 posts

Re: The End of the Redis Adventure

#31

Earlier quoted context omitted.

> What is "underground programming world"? If you have to ask... ;)

We're all violating the first and second rules of "underground programming world"

I'd expect the underground programming world to index from zero.

Re: The End of the Redis Adventure

#32
Redis has given me more than the occasional headache when it comes to its lax security defaults and how since it's going to be local then why bother changing them? But there's no denying that when it works, it works damnably well. So for that, I give you my thanks and good luck in whatever endeavors you find yourself involved in!

Re: The End of the Redis Adventure

#33
@antirez - thank you so much for your work, and for your patience with dealing with us all over the years. I have benefited greatly from your willingness to share your engineering skills, and you are one of the most respected programmers in my list of people to follow online.

So, onwards and upwards to new things. Perhaps now you have time for my favourite of your projects, LOAD81? :)

Re: The End of the Redis Adventure

#35

Dang. I say this frequently both online and when discussing system design with newer devs, but will repeat here: of all the production issues I've debugged, the culprit has has never been redis. In fact, redis has been a critical piece of achieving cost-effective scaling. It is one of only two pieces of software (along with postgres) that I blindly recommend without any caveats. From following along here and on your…

Redis is simple. Good. Has a nice api. Has good libraries. Single threadsed. Extremely hard to scale. Impossibly difficult to cluster in containers because it uses hard coded ips to address nodes. Performs poorly with large payloads. Doesn't run on windows properly. Is extremely expensive as a hosted service (orders of magnitude in some cases, eg. azure).

You'll love it until you don't.

The scaling and clustering story is not nearly as nice as the quick start.

It's definitely worth recommending... with caveats.

Re: The End of the Redis Adventure

#36

Dang. I say this frequently both online and when discussing system design with newer devs, but will repeat here: of all the production issues I've debugged, the culprit has has never been redis. In fact, redis has been a critical piece of achieving cost-effective scaling. It is one of only two pieces of software (along with postgres) that I blindly recommend without any caveats. From following along here and on your…

Redis is simple. Good. Has a nice api. Has good libraries. Single threadsed. Extremely hard to scale. Impossibly difficult to cluster in containers because it uses hard coded ips to address nodes. Performs poorly with large payloads. Doesn't run on windows properly. Is extremely expensive as a hosted service (orders of magnitude in some cases, eg. azure). You'll love it until you don't. The scaling and clustering sto…

> Is extremely expensive as a hosted service (orders of magnitude in some cases, eg. azure).

That seems to me an argument that should be pointed at cloud providers rather than Redis itself ;)

Re: The End of the Redis Adventure

#38

First and foremost thanks and good luck @antirez, your comments and pointers here have been nothing less than amazing. On a more selfish note, how is this going to affect Redis development?

Looks like they’re already well covered with community contributions and two new (or pre-existing) maintainers?

Re: The End of the Redis Adventure

#39
Thank you! In building Redis you’ve contributed some wonderful software to the world. In addition, I’ve always found your blogs to be interesting reads. I’ve also learned by the examples you set both from a coding perspective (reading your wcode), and engineering perspective. Thank you again, looking forward to whatever is next!

Re: The End of the Redis Adventure

#40
post #4

@antirez - Thank you for Redis! It's been a joy to use across so many projects. > However I never wanted to be a software maintainer. And nothing say that you have to be. There's this perverted view that anytime someone creates a popular FOSS project, they need to dedicate every waking minute to maintaining it. That's neither economically feasible nor psychologically reasonable. > Redis was the most stressful thing I…

I was also intrigued by that sentence. I expect it means (open source) programming that happens outside of of big corps.

But I'm unsure.

Post reply on HN