: #1 is a trade off against being possibly more available to writes in the case : of a single down node. In the cloud case, you're still open for business. In : the classical replication case, you're no longer available for writes if the : downed node is the master.
or to put it another way: classic replication lets you use N nodes for high availability reads, but you have a single point of failure for writes. solr cloud gives you high availability for reads and writes -- including NRT support -- at the expense of more network overhead when writes happen. : > -is solrcloud w/o sharding done?( I.e. "it's just not done!!" ) : > -any downside (i.e. aside from the lack of horizontal scalability ) it is certainly done -- specifically it is a matter of creating a collection with numShards=1 and replicationFactor=N. -Hoss http://www.lucidworks.com/
