# Embedded usage **URL:** \ **Category:** Elasticsearch\ **Created:** [May 9, 2010, 11:49am UTC](https://discuss.elastic.co/t/embedded-usage/2943 "2010-05-09T11:49:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Sten\_Roger\_Sandvik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sten_roger_sandvik/32/2893_2.png) [@Sten\_Roger\_Sandvik](https://discuss.elastic.co/u/Sten_Roger_Sandvik)\ **Post date:** [May 9, 2010, 11:49am UTC](https://discuss.elastic.co/t/embedded-usage/2943/1 "2010-05-09T11:49:36Z")
Hi. I came across ElasticSearch some weeks ago and it looks great. My company is now in the process of embedding a Lucene search into our product. Now it's time to figure out how to best cluster a beast like Lucene. ElasticSearch seems to be the best candidate. But, anyone has any experience on embedding it? Is it possible to integrate with different cluster messaging transports? Need to coordinate the settings with different parts of the system. Regards, Sten Roger Sandvik ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 9, 2010, 5:09pm UTC](https://discuss.elastic.co/t/embedded-usage/2943/2 "2010-05-09T17:09:18Z")
Hi, Elasticsearch is very customizable and should be easily embeddable. If you can give more details or specific requirements, I can try and help with some examples. What do you mean by different cluster messaging transports? cheers, shay.banon On Sun, May 9, 2010 at 2:49 PM, Sten Roger [stenrs@gmail.com](mailto:stenrs@gmail.com) wrote: > Hi. > > I came across Elasticsearch some weeks ago and it looks great. My > company is now in the process of embedding a Lucene search into our > product. Now it's time to figure out how to best cluster a beast like > Lucene. Elasticsearch seems to be the best candidate. > > But, anyone has any experience on embedding it? Is it possible to > integrate with different cluster messaging transports? Need to > coordinate the settings with different parts of the system. > > Regards, > Sten Roger Sandvik ---
**Author:** ![Sten\_Roger\_Sandvik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sten_roger_sandvik/32/2893_2.png) [@Sten\_Roger\_Sandvik](https://discuss.elastic.co/u/Sten_Roger_Sandvik)\ **Post date:** [May 9, 2010, 5:15pm UTC](https://discuss.elastic.co/t/embedded-usage/2943/3 "2010-05-09T17:15:35Z")
> Elasticsearch is very customizable and should be easily embeddable. If you > can give more details or specific requirements, I can try and help with some > examples. What do you mean by different cluster messaging transports? Well, what I need is some way to patch into the cluster discovery mechanism or to use the same as wee do (JGroups). /srs ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 9, 2010, 5:17pm UTC](https://discuss.elastic.co/t/embedded-usage/2943/4 "2010-05-09T17:17:18Z")
JGroups is used in elasticsearch already, though as a plugin from the next release since it is replaced with a custom built discovery module. You can have a look at the JGroupsDiscovery class. Do you want to share the same channel? cheers, shay.banon On Sun, May 9, 2010 at 8:15 PM, Sten Roger [stenrs@gmail.com](mailto:stenrs@gmail.com) wrote: > > Elasticsearch is very customizable and should be easily embeddable. If > > you > > can give more details or specific requirements, I can try and help with > > some > > examples. What do you mean by different cluster messaging transports? > > Well, what I need is some way to patch into the cluster discovery > mechanism or to use the same as wee do (JGroups). > > /srs ---
**Author:** ![Sten\_Roger\_Sandvik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sten_roger_sandvik/32/2893_2.png) [@Sten\_Roger\_Sandvik](https://discuss.elastic.co/u/Sten_Roger_Sandvik)\ **Post date:** [May 9, 2010, 5:25pm UTC](https://discuss.elastic.co/t/embedded-usage/2943/5 "2010-05-09T17:25:35Z")
On May 9, 7:17 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > JGroups is used in elasticsearch already, though as a plugin from the next > release since it is replaced with a custom built discovery module. You can > have a look at the JGroupsDiscovery class. Do you want to share the same > channel? Cool. I will have a look at JGroupsDiscovery class. Yes, want to share the same channel so it's easier for customers to configure the whole application. /srs ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 9, 2010, 5:27pm UTC](https://discuss.elastic.co/t/embedded-usage/2943/6 "2010-05-09T17:27:33Z")
Sharing the same channel will require some work to filter out messages that are not required. I will be happy to include a generic solution for this in JgroupsDiscovery if you do change it in Elasticsearch. cheers, shay.banon On Sun, May 9, 2010 at 8:25 PM, Sten Roger [stenrs@gmail.com](mailto:stenrs@gmail.com) wrote: > On May 9, 7:17 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote: > > > JGroups is used in elasticsearch already, though as a plugin from the > > next > > release since it is replaced with a custom built discovery module. You > > can > > have a look at the JGroupsDiscovery class. Do you want to share the same > > channel? > > Cool. I will have a look at JGroupsDiscovery class. Yes, want to share > the same channel so it's easier for customers to configure the whole > application. > > /srs ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:24am UTC](https://discuss.elastic.co/t/embedded-usage/2943/7 "2017-07-06T04:24:12Z")