What would be a compelling reason to use this over native ES and vice
versa?
Thanks.
On Thu, Jun 10, 2010 at 5:04 AM, sd samueldoyle@gmail.com wrote:
What would be a compelling reason to use this over native ES and vice
versa?
As far as I cat tell, there's no advantage per se by using an embedded
ES instance.
But, by embedding ES into your own product, you could avoid double
operational costs, plus, obviously, add search engine capabilities in
a somewhat integrated way.
Talking about Terrastore and Elastic Search integration, the real
advantage isn't in having an embedded ES server (with its own port and
alike) into Terrastore: you could indeed shutdown the embedded HTTP ES
interface and embedded ES storage (by properly configuring the
properties file), and relay on external ES instances; this way,
Terrastore would transparently delegate all index operations to
external ES instances, so again, you'd still have an integrated
solution for distributed storage and indexing.
Hope things are a bit clearer now, just let us know if you have other questions.
Cheers,
Sergio B.
--
Sergio Bossa
http://www.linkedin.com/in/sergiob