4 ms·

Woohoo! Redis has quickly become my favorite transient data store. I'm using a combination of Postgres, Redis and Cassandra and feel like I have the natural dat

by geoffc 16y ago

Woohoo! Redis has quickly become my favorite transient data store. I'm using a combination of Postgres, Redis and Cassandra and feel like I have the natural data mapping for every scenario. No more pushing square pegs into round holes.

mcav 16y ago
What are the advantages of Redis over Cassandra? (honest question)
- geoffc 16y ago
  Redis has a rapidly growing list of data operations to model a wide variety of problems within a bound storage space (the VM feature expands that space). Cassandra does a specific task, unlimited high volume redundant writes, extremely well. I use Redis for session data, caching and queuing needs but for the huge volume data store Cassandra is the answer. Redis is a swiss army knife, Cassandra is a Ka-Bar.
  - Nwallins 16y ago
    http://en.wikipedia.org/wiki/KA-BAR http://en.wikipedia.org/wiki/KA-BAR for those interested...
- amix 16y ago
  * Redis is a lot simpler and more dynamic since it isn't intended to solve petabyte problems or used on large clusters of computers. An example, you can play with Redis online: http://try.redis-db.com/ http://try.redis-db.com/ * Redis is much easier to understand, since Redis is a key-value store with rich datatypes (such as lists, sets and hashes). Cassandra is a database paradigm shift build to solve Google scale problems. * Redis perfomance is similar to memcached - and memcached's perfomance is pretty amazing. I would only pick something like Cassandra if I had to store a lot of data on a large number of computers. If I wanted to do something fast and I know that my data won't grow to terabytes then Redis is a very good choice.
samstokes 16y ago
I don't suppose you'd consider blogging about that setup (and in particular which data store you find to be natural for which scenario)? I don't know Redis or Cassandra (or similar) very well, which means it's hard to know what sort of things they're best suited to, compared to each other or to an RDBMS.
- geoffc 16y ago
  At some point I would like to blog about it but right now I am under the gun to deliver a product so I'm writing a lot more code than english for the next few months. In a nutshell I use Postgres for the relatively static data and Cassandra for the very high volume transactional data. I use Redis for ad-hoc data structures and some caching. The natural fit means I'm not jamming de-normalized data into a relational database for performance reasons. Hope this helps.
  - samstokes 16y ago
    Yes, that's useful - thanks!

by geoffc 16y ago

mcav 16y ago

What are the advantages of Redis over Cassandra? (honest question)

geoffc 16y ago
Redis has a rapidly growing list of data operations to model a wide variety of problems within a bound storage space (the VM feature expands that space). Cassandra does a specific task, unlimited high volume redundant writes, extremely well. I use Redis for session data, caching and queuing needs but for the huge volume data store Cassandra is the answer. Redis is a swiss army knife, Cassandra is a Ka-Bar.
- Nwallins 16y ago
  http://en.wikipedia.org/wiki/KA-BAR http://en.wikipedia.org/wiki/KA-BAR for those interested...
amix 16y ago
* Redis is a lot simpler and more dynamic since it isn't intended to solve petabyte problems or used on large clusters of computers. An example, you can play with Redis online: http://try.redis-db.com/ http://try.redis-db.com/ * Redis is much easier to understand, since Redis is a key-value store with rich datatypes (such as lists, sets and hashes). Cassandra is a database paradigm shift build to solve Google scale problems. * Redis perfomance is similar to memcached - and memcached's perfomance is pretty amazing. I would only pick something like Cassandra if I had to store a lot of data on a large number of computers. If I wanted to do something fast and I know that my data won't grow to terabytes then Redis is a very good choice.

samstokes 16y ago

I don't suppose you'd consider blogging about that setup (and in particular which data store you find to be natural for which scenario)? I don't know Redis or Cassandra (or similar) very well, which means it's hard to know what sort of things they're best suited to, compared to each other or to an RDBMS.

geoffc 16y ago
At some point I would like to blog about it but right now I am under the gun to deliver a product so I'm writing a lot more code than english for the next few months. In a nutshell I use Postgres for the relatively static data and Cassandra for the very high volume transactional data. I use Redis for ad-hoc data structures and some caching. The natural fit means I'm not jamming de-normalized data into a relational database for performance reasons. Hope this helps.
- samstokes 16y ago
  Yes, that's useful - thanks!