You probably get this a lot, but I'm going to say it anyway - Thank you for redis, it's an amazing bit of software and I use it in virtually every project.
Not only is it useful, but the source code is pure poetry to read.
Just to pile on the praise, I've learned more about the C language reading Redis' source code than I've learned from two books, a university course, and dozens of blog posts combined. Keep doing what you're doing, it is an inspiration.
OMG that's awesome. And a bit surprising since Redis internals could be much much better, if we only could care a bit less about memory / CPU / copy-on-write issues, and... a bit more time :-)
Redis itself is great, but the fact that it keeps getting better is what truly amazes me. There have been features added that I never though I would use, that I find myself building into and on top of later.
As someone who created & maintains an open source project (not nearly as important or popular as redis), thank you for your comment. You'd be surprised how few compliments people get on OSS projects (it seems to be roughly one heartfelt, sincere comment per 20,000 users in my case) and they just make you feel amazing. Seriously, the last one I had made my week.
I just read the about page. Could you help me understand a little more about how it works? It seems like a tool that could replace sessions and cookies, and possibly a browser-based database?
My current project is a tournament-scoring app where I'm using cookies to hold match scores, so that the score won't be lost if the page is refreshed before the match is over and saved to the database. Would redis be appropriate in that context?
I'm not associated with redis, but I do use it daily. It's basically just a really good in memory db. You can use it for almost anything, from job queues, to message brokering, to session storage. Check out the different language clients, find you language of choice and read about how to fire it up and try it out https://redis.io/clients.
For example Celery supports a large number of message brokers, and a lot of people inexperienced with message passing etc. will use Redis as a broker because they already are familiar with it and running it in production. I myself made that mistake, and have since gotten much better results with the aforementioned change. So while it should seem obvious, theirs a lot of places where it is still accidentally done.
It would be for keeping cookies, sessions and ranks there. I am doing exactly that with Redis and it's ultra fast and easy. Redis has special data structure for what you want to do, it's sorted set, check it out
Not only is it useful, but the source code is pure poetry to read.
Thank you again