Redis vs. Mongo DB – The battle of the NoSQL databases continues
1–10 of 21 posts
Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#2Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#3Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#4Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#5Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#6Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#7I thought Redis was a cache, not a database.
Really this article is dumb. I think almost never would you need to choose redis vs mongo.
Redis is a weird and hard to describe product. For example you can use it as a queue over rabbitmq with celery. Or a cache with all kinds of things. But it does more. And an empty instance runs in like 3mb of ram and handles thousands of connections.
Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#8Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#9Love the sport of Redis combined with the flexibility of Mongo.
Re: Redis vs. Mongo DB – The battle of the NoSQL databases continues
#10- Leaderboard: Redis shines when we need to store ranking data. - Geo Query: Instead of query geo spatial index directly from MongoDB. I use Redis and feed the id back into MongoDB - Track Occurence Of Event: Let's say we need to keep track state of an user - Set of data
In other words, I treat Redis as a network/distributed data structure, which I can implement in the main db, but will require heavy read/write.