I have heard a lot of times about redis in the past but I had never had a deep look into it. This tutorial answered a lot of my questions and maybe will do the same for you to:
I've carefully read Redis's features, and while I find it interesting, I haven't yet found an application that could truly benefit from it
Probably, as long as we're talking about small databases (few hundred-thousand tables and a few million rows), the difference with traditional db servers isn't noticeable
Have any of you used it?
What exactly do you use it for?
I've carefully read Redis's features, and while I find it interesting, I haven't yet found an application that could truly benefit from it
Probably, as long as we're talking about small databases (few hundred-thousand tables and a few million rows), the difference with traditional db servers isn't noticeable
Have any of you used it?
What exactly do you use it for?
I have heard a single sentence that sums up the whole basic use of Redis. This sentence is: "The fastest query is the query that will not be executed". In a nutshell: "It is a caching layer for data in a basic approach and expanding it with modules, as you saw, can be used for all types of databases". This is also a benefit: Common data interface for different kind of DBs. Further more connecting each handler of a webapp directly with the database, for a very busy application, the maximum number of connections might quickly be exausted. With several instances of redis you increase dramatically the maximum amount of concurrent users that can "query" the same data.