On Thu, Sep 9, 2010 at 1:20 AM, Jonathan Rochkind <rochk...@jhu.edu> wrote: > You _could_ use SolrJ with EmbeddedSolrServer. But personally I wouldn't > unless there's a reason to. There's no automatic reason not to use the > ordinary Solr HTTP api, even for an in-house application which is not a web > application. Unless you have a real reason to use embedded solr, I'd use the > HTTP api, possibly via SolrJ if your local application is Java.
Right. Some people associate HTTP with "slow", but it's just not so. HTTP is just a TCP socket with some small standard headers. Solr can even talk binary over HTTP so there isn't even text or XML parsing overhead. Think of it like a database - the norm is to run it as a separate server process. Embedding is only something you should do if you have really "interesting" requirements. -Yonik http://lucenerevolution.org Lucene/Solr Conference, Boston Oct 7-8
