I'm definitely interested in what you've built.
I'm working on more advanced Redis use case patterns and your project fits in with that theme.
I'm working on more advanced Redis use case patterns and your project fits in with that theme.
Its interesting how much you can actually do with Redis for. We actually implemented binary search in the indexing engine so you can do non-equality searches against sorted tables of strings.
I haven't found much you can't do with Redis that you can do with other NoSQL databases. And with the cost of RAM and motherboards that support huge amounts of RAM going down, you can index huge amounts of data in RAM and then just hammer it.
I'm working on common use cases from leaderboards, profiles/sessions, voting, latest items, followers, and who's online. On the more advanced end, I have a use case for secondary indexes in queue but have not started working on these yet.
> Its interesting how much you can actually do with Redis for.
I fully agree. Using Redis for only simple use cases greatly under utilizes its capabilities.
I think basically you can use it just like any other database, you just have to write some more code sometimes. We actually have binary search for it in our indexing engine so you can use it for non-equality searches on arbitrary strings.
We might see it used more often with the cost of RAM going down. I think the high cost of RAM in the cloud is an issue though. I have 64gb RAM servers in my basement that cost $200, but the same server on the cloud would cost thousands of dollars a year to rent.