The fact that I ignore Cassandra is because of it seems Cassandra is perfect when you have too much write operation. In my case it is true that I have some update operation but for sure read operations are much more than write ones. By the way there are probably more scenarios for my application. My question would be which one is probably the best? Best regards.
On Mon, May 26, 2014 at 6:27 PM, Jack Krupansky <j...@basetechnology.com>wrote: > You could also consider DataStax Enterprise, which integrates Apache > Cassandra as the primary database and Solr for indexing and query. > > See: > http://www.datastax.com/what-we-offer/products-services/ > datastax-enterprise > > -- Jack Krupansky > > -----Original Message----- From: Ali Nazemian > Sent: Monday, May 26, 2014 9:50 AM > To: solr-user@lucene.apache.org > Subject: Using SolrCloud with RDBMS or without > > > Hi everybody, > > I was wondering which scenario (or the combination) would be better for my > application. From the aspect of performance, scalability and high > availability. Here is my application: > > Suppose I am going to have more than 10m documents and it grows every day. > (probably in 1 years it reaches to more than 100m docs. I want to use Solr > as tool for indexing these documents but the problem is I have some data > fields that could change frequently. (not too much but it could change) > > Scenarios: > > 1- Using SolrCloud as database for all data. (even the one that could be > changed) > > 2- Using SolrCloud as database for static data and using RDBMS (such as > oracle) for storing dynamic fields. > > 3- Using The integration of SolrCloud and Hadoop (HDFS+MapReduce) for all > data. > > Best regards. > > -- > A.Nazemian > -- A.Nazemian
