I have to agree with Tatu. If you're struggling to find reasons to validate that Cassandra is the better choice for your task than Solr, then perhaps Solr is the correct choice. I kind of went through the same thing recently, struggled to make Cassandra fit what I was doing, then realized I was doing it wrong and moved to MongoDB.
Cassandra is great at what it tries to accomplish, which is managing gigantic datasets in a distributed way. The question is, is that really what you need? On Thu, Jan 7, 2010 at 12:58 PM, Tatu Saloranta <tsalora...@gmail.com>wrote: > On Thu, Jan 7, 2010 at 3:16 AM, Richard Grossman <richie...@gmail.com> > wrote: > > Hi, > > > > This message is little different than support. > > I'm confronted to problem where people want to change Cassandra with Solr > > server. I really think that our problem is a great case for cassandra but > I > > need more arguments. > > > > So please if you've some time just put some idea why to use cassandra > > instead solr. > > Solution is generally applicable to a problem... so what is the (main) use > case? > > That would make it easier to find arguments for or against proposed > solution. > > -+ Tatu +- >
