Re:MongoDB vs Redis, a different interpretation of what's wr...
by moe on Thursday June 04, 2009 @10:30AM
(#641428)
Even without the persistence you can say something is a database. It's not a coincidence that the term "in memory database" exists for example.
Then why is redis not advertised as an "in memory database"?
It likes to be compared with MongoDB or TokyoTyrant but is clearly not playing in the same league.
Moreover it glosses over this issue in quite a self-righteous fashion almost everywhere. One example of many would be this gem from the "TwitterAlikeExample":
This means you can serve millions of users every day with just a single Linux
box, and this one was monkey asses slow!
That's just false advertising if your "millions of users" actually use the service. Just storing the plain account data for 1 million users would push the database into the 1GB realm. Go figure what happens when these users actually begin to leave a footprint.
Btw everything is used to store data permantly, reliably or not for your specific needs/tastes, is a database.
I'm not normally nitpicking about terminology. It just left a bad taste in my mouth in this particular case because the redis homepage doesn't bother to mention this critical difference to most similar offerings. The current blurb is highly deceptive.
Then why is redis not advertised as an "in memory database"? It likes to be compared with MongoDB or TokyoTyrant but is clearly not playing in the same league.
Moreover it glosses over this issue in quite a self-righteous fashion almost everywhere. One example of many would be this gem from the "TwitterAlikeExample":
This means you can serve millions of users every day with just a single Linux box, and this one was monkey asses slow!
That's just false advertising if your "millions of users" actually use the service. Just storing the plain account data for 1 million users would push the database into the 1GB realm. Go figure what happens when these users actually begin to leave a footprint.
Btw everything is used to store data permantly, reliably or not for your specific needs/tastes, is a database.
I'm not normally nitpicking about terminology. It just left a bad taste in my mouth in this particular case because the redis homepage doesn't bother to mention this critical difference to most similar offerings. The current blurb is highly deceptive.