Not sure if it's a good argument, but cost is the reason. By keeping the base implementation in a permanent, local instance, cost is supposed to be less.
Dennis Gearon Signature Warning ---------------- EARTH has a Right To Life, otherwise we all die. Read 'Hot, Flat, and Crowded' Laugh at http://www.yert.com/film.php --- On Sun, 4/25/10, Otis Gospodnetic <otis_gospodne...@yahoo.com> wrote: > From: Otis Gospodnetic <otis_gospodne...@yahoo.com> > Subject: Re: hybrid approach to using cloud servers for Solr/Lucene > To: solr-user@lucene.apache.org > Date: Sunday, April 25, 2010, 9:30 PM > Hi, > > Hm. Everything is doable, but this sounds a bit > undefined and possibly messy. If flexibility is of > such importance, why have the "local" part at all? Why > not have everything in an elastic cloud environment? > Otis > ---- > Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch > Lucene ecosystem search :: http://search-lucene.com/ > > > > ----- Original Message ---- > > From: Dennis Gearon <gear...@sbcglobal.net> > > To: solr-user@lucene.apache.org > > Sent: Sun, April 25, 2010 10:17:11 PM > > Subject: hybrid approach to using cloud servers for > Solr/Lucene > > > > I'm working on an app that could grow much faster and > bigger than I could scale > > local resources, at least on certain dates and for > other reasons. > > So I'd > > like to run a local machine in a dedicated host or > even virtual machine at a > > host. > > If the load goes up, then queries are sent to the cloud at > a > > certain point. > > Is this practical, anyone have experience in > > this? > > This is obviously a search engine app based on solr/lucene > if > > someone is wondering. > > Dennis Gearon > > Signature > > Warning > ---------------- > EARTH has a Right To Life, > otherwise we > > all die. > > Read 'Hot, Flat, and Crowded' > Laugh at > > href="http://www.yert.com/film.php"; > target=_blank > > >http://www.yert.com/film.php >
