I can give you a few more data points. For one of my last projects, I
built the search index of one of the largest IM aggregators. I got
around 2.5k chat msg/s, keeping 400M messages in my index.
I looked at Solr and while it is very convenient/luxurious, there was
no way in hell I could scale it
Good point although there has been very recent work integrating solr with
katta so you can have your cake and eat it too:
http://developer.yahoo.net/blogs/theater/archives/2009/12/hadoop_bay_area_user_group_session_1.html
On Fri, Jan 8, 2010 at 1:09 AM, Erich Nachbar er...@nachbar.biz 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
things positive for solr.
- mature and stable
- lots of documentation
- a swiss army knife and can be used for a LOT of things, especially if you are
manipulating a lot of text.
- the query language is easier to use (imho.. but i've been using solr for
years, so I am biased)
- lots of people
On Thu, Jan 7, 2010 at 10:43 AM, Nathan McCall n...@vervewireless.com wrote:
Agreed that there is not much to go on here in the original question.
I will say that we very recently found a good fit with Solr and
Cassandra in how we deal with a very heavy write volume of news
article data.
First Thanks to all your answer it's help to really check all the aspects.
- In fact the system we want to build have to manage a lot of data but
not in an heavy transactional way. Solr can handle the data but doesn't have
the distributed way to serve it. But it's always possible to
