11–20 of 29 posts
I wonder if being part of Facebook (from which Cassandra originated) has anything to do with the choice for Cassandra over other databases.
[1] http://nosql.mypopescu.com/post/1583884165/facebook-the-unde...
I'm interested if @antirez has thought of extending the (admittedly fun) redis api to a disk-backed version for when you don't need the performance of in-memory, but appreciate the simplicity of the redis api. Maybe be able to assign a specific DB number to disk? I realize that might be kitchen sinking Redis more than he intends, but it might be worth it.
I assume Instagram was a serious user of Redis. If you can switch from Redis to Cassandra in a matter of days, even after presumably years of Redis-usage being ground in your code base (because no matter how much you try to abstract out your fundamental data store, it always comes poking out in your architecture), it's probably not useful for Redis to try to out-Cassandra Cassandra. Let Redis be the best Redis it can…
I'm interested if @antirez has thought of extending the (admittedly fun) redis api to a disk-backed version for when you don't need the performance of in-memory, but appreciate the simplicity of the redis api. Maybe be able to assign a specific DB number to disk? I realize that might be kitchen sinking Redis more than he intends, but it might be worth it.
http://www.anchor.com.au/blog/2013/04/redis-rethought-exciti...;
Just to be clear -- this doesn't mean we have eliminated Redis. It's still a very useful tool.
Awesome interview and kudos to whoever recommended the switch, that's a ton of savings you guys made!
I'm interested if @antirez has thought of extending the (admittedly fun) redis api to a disk-backed version for when you don't need the performance of in-memory, but appreciate the simplicity of the redis api. Maybe be able to assign a specific DB number to disk? I realize that might be kitchen sinking Redis more than he intends, but it might be worth it.
I'm interested if @antirez has thought of extending the (admittedly fun) redis api to a disk-backed version for when you don't need the performance of in-memory, but appreciate the simplicity of the redis api. Maybe be able to assign a specific DB number to disk? I realize that might be kitchen sinking Redis more than he intends, but it might be worth it.
However that said it is also true that memory starts to be seriously cheap, and the real limit may be to run stuff on EC2 or similar platforms.
So sometimes the cost of RAM is a virtual cost associated with the platform you are running your services in, compared to the actual cost of that amount of memory.
I'm interested if @antirez has thought of extending the (admittedly fun) redis api to a disk-backed version for when you don't need the performance of in-memory, but appreciate the simplicity of the redis api. Maybe be able to assign a specific DB number to disk? I realize that might be kitchen sinking Redis more than he intends, but it might be worth it.
The article compares Redis to Cassandra which means comparing apples to oranges for their use case. It would have been meaningful if they explained why they chose Casssandra, instead of for example Hbase.
"We are very happy with the hammer we are currently using. Previously, we were using pliers to hammer nails and we saw that it wasn't very efficient."