The underlying data structures it provides are the building blocks of high-performance DB systems.Д¬aching using MongoDB simply doesn't make a lot of sense. That's one use case where you would typically prefer MongoDB. Redis is simply faster, but not suited for prototyping. To put it in a nutshell, Redis and MongoDB can be used in order to achieve similar things. Sets, Hashes, Lists), but you have to explicitly define how you want to store you data. Redis provides a bunch of useful data structures (e.g.

Redis does not make any assumptions based on your data. Antirez (developer of Redis) demonstrated using Lamernews that it is indeed possible to use Redis as a stand alone database system. Websites like Craigslist use Redis next to their primary database. It is very uncommon to use Redis as a standalone database system (some people prefer referring to it as a 'key-value'-store). Redis can be easily integrated as a LRU cache. Use Redis in order to speed up your existing application. Its performance is not that great and can't be compared to Redis. Besides that, MongoDB is great for prototyping or trying things out. It simply means that your schema needs to be defined in your app (e.g. While MongoDB is schemaless and non-relational, this does not mean that there is no schema at all. MongoDB does not make any assumptions on your underlying schema. MongoDB is suited for Hackathons, startups or every time you don't know how you'll query the data you inserted. Use MongoDB if you don't know yet how you're going to query your data. Nevertheless, I consider the following aspects to be worth adding: I just noticed that this question is quite old. If you ask me, my personal choice is Redis for most requirements. For more schema-able data, MongoDB is better. A cache layer can probably be better implemented in Redis. However, Redis's non-traditional approach requires more effort to learn, but greater flexibility.Д®g. MongoDB offers simplicity, much shorter learning curve for developers with traditional DB and SQL experience. On the other hand, in Redis, sheer speed of the response to those queries is the payoff for the extra work of dealing with the variety of structures your data might be stored with. In MongoDB the same queries might be easier because the structure is more consistent across your data. I would say, it depends on kind of dev team you are and your application needs.ДЇor example, if you require a lot of querying, that mostly means it would be more work for your developers to use Redis, where your data might be stored in variety of specialized data structures, customized for each type of object for efficiency.

Druid vs arangodb