4 ms·

At the place where I work it's become clear that we need something like cassandra or redis. The lack of robustness in the php redis client is a cause for concer

by wanderr 17y ago

At the place where I work it's become clear that we need something like cassandra or redis. The lack of robustness in the php redis client is a cause for concern for me (as compared to libmemcached), and I don't know much about cassandra, but our CTO opposes it because he thinks the documentation is spotty and not enough big projects are using it. Thoughts?

jseifer 17y ago
Your CTO is right. I was recently in the position of using Tokyo Cabinet on a site with a lot of traffic. Initially, it was great. It continued to be great for a long while until we hit a point where it started taking up too much memory and 100% cpu causing load to sky rocket. While the technology is great, there was very little that Google found about our particular problem. We eventually wound up resetting our tyrant database and plan on moving completely off of it.
- whargarbl 17y ago
  You didn't strace it to see what was going on?
jbellis 17y ago
> documentation is spotty True, but we're working on that (and we're very responsive on IRC and mailing lists). > not enough big projects are using it I don't think that's true anymore; Digg, Facebook, Rackspace, Twitter, Mahalo, Ooyala, SimpleGeo, WebEx, and others are using Cassandra: http://n2.nabble.com/Cassandra-users-survey-td4040068.html http://n2.nabble.com/Cassandra-users-survey-td4040068.html
- wanderr 17y ago
  Thanks for the link, it will be useful if I try to make a case for cassandra vs redis. Other questions: how robust are the clients (especially for php), and are you aware of any performance/scaling comparisons between cassandra and redis?
  - jbellis 17y ago
    the clients are thrift, and the commonly used ones (java, python, ruby, C++, php), are robust, although the thrift devs are slow to apply patches sometimes (all the php users I know have applied http://issues.apache.org/jira/browse/THRIFT-347 http://issues.apache.org/jira/browse/THRIFT-347). redis is faster per node, but does not scale, there is not much to compare. :)

by wanderr 17y ago

jseifer 17y ago

Your CTO is right. I was recently in the position of using Tokyo Cabinet on a site with a lot of traffic. Initially, it was great. It continued to be great for a long while until we hit a point where it started taking up too much memory and 100% cpu causing load to sky rocket. While the technology is great, there was very little that Google found about our particular problem. We eventually wound up resetting our tyrant database and plan on moving completely off of it.

whargarbl 17y ago
You didn't strace it to see what was going on?

jbellis 17y ago

> documentation is spotty True, but we're working on that (and we're very responsive on IRC and mailing lists). > not enough big projects are using it I don't think that's true anymore; Digg, Facebook, Rackspace, Twitter, Mahalo, Ooyala, SimpleGeo, WebEx, and others are using Cassandra: http://n2.nabble.com/Cassandra-users-survey-td4040068.html http://n2.nabble.com/Cassandra-users-survey-td4040068.html

wanderr 17y ago
Thanks for the link, it will be useful if I try to make a case for cassandra vs redis. Other questions: how robust are the clients (especially for php), and are you aware of any performance/scaling comparisons between cassandra and redis?
- jbellis 17y ago
  the clients are thrift, and the commonly used ones (java, python, ruby, C++, php), are robust, although the thrift devs are slow to apply patches sometimes (all the php users I know have applied http://issues.apache.org/jira/browse/THRIFT-347 http://issues.apache.org/jira/browse/THRIFT-347). redis is faster per node, but does not scale, there is not much to compare. :)