# Modularization of elastic search on maven central

**URL:** <https://discuss.elastic.co/t/modularization-of-elastic-search-on-maven-central/5070>\
**Category:** Elasticsearch\
**Created:** [August 5, 2011, 5:49pm UTC](https://discuss.elastic.co/t/modularization-of-elastic-search-on-maven-central/5070 "2011-08-05T17:49:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frederic\_Camblor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frederic_camblor/32/3150_2.png) [@Frederic\_Camblor](https://discuss.elastic.co/u/Frederic_Camblor)\
**Post date:** [August 5, 2011, 5:49pm UTC](https://discuss.elastic.co/t/modularization-of-elastic-search-on-maven-central/5070/1 "2011-08-05T17:49:56Z")

</div>

Hi everyone 🙂

I was simply wondering if it was planned to modularize the elastic search  
artefact present on maven central ?  
For now, the org.elasticsearch:elasticsearch:0.17.4 takes approximatively  
11Mo.

I'm only using the java client API and I'm wondering if the full 11Mo bundle  
are useful for the java api only ?  
Will you plan to lower this and provide a much thiner archive ("a la"  
spring) allowing to choose which component to integrate in our application ?

Thanks in advance for your feedback 🙂

Frédéric

---

<div class="post-metadata">

**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:** [August 5, 2011, 7:36pm UTC](https://discuss.elastic.co/t/modularization-of-elastic-search-on-maven-central/5070/2 "2011-08-05T19:36:05Z")

</div>

Yea..., its a hefty jar... . The main reason why the jar is a big one is  
because elasticsearch is almost completely evented. This menas a lot of  
small, sometimes inner classes, and Java does a bad job compressing it (its  
zip based, compression is per class file).

Another smaller reason is that elasticsearch embeds most of the libs it uses  
(except for Lucene), this include mainly jackson, netty, and guice. This  
allows for elasticsearch to use its own verified version of those libraries.

So, to answer your question, no, there won't be a smaller jar file in the  
future.

2011/8/5 Frédéric Camblor [fcamblor@gmail.com](mailto:fcamblor@gmail.com)

> Hi everyone 🙂
> 
> I was simply wondering if it was planned to modularize the Elasticsearch  
> artefact present on maven central ?  
> For now, the org.elasticsearch:elasticsearch:0.17.4 takes approximatively  
> 11Mo.
> 
> I'm only using the java client API and I'm wondering if the full 11Mo  
> bundle are useful for the java api only ?  
> Will you plan to lower this and provide a much thiner archive ("a la"  
> spring) allowing to choose which component to integrate in our application ?
> 
> Thanks in advance for your feedback 🙂
> 
> Frédéric

---

<div class="post-metadata">

**Author:** ![Roberto\_Franchini](https://avatars.discourse-cdn.com/v4/letter/r/7c8e57/32.png) [@Roberto\_Franchini](https://discuss.elastic.co/u/Roberto_Franchini)\
**Post date:** [August 9, 2011, 4:45pm UTC](https://discuss.elastic.co/t/modularization-of-elastic-search-on-maven-central/5070/3 "2011-08-09T16:45:33Z")

</div>

On Fri, Aug 5, 2011 at 9:36 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:  
[cut]

> So, to answer your question, no, there won't be a smaller jar file in the  
> future.

## Hi, I'm evaluating ES. I understand your needs, but could you split the client part of the jar from the server part? Is it possible to do that without a lot of effort? Cheers, RF

Roberto Franchini  
L'impossibile è inevitabile.  
[http://www.celi.it](http://www.celi.it)

> **[Blogmeter - Integrated Social Intelligence](https://blogmeter.it/)**
>
> Blogmeter fornisce una piattaforma proprietaria integrata di social intelligence - la Blogmeter Suite - ed è specializzata in ricerche di mercato e analisi dei social media e del web.

Tel +39.011.562.71.15  
[jabber:ro.franchini@gmail.com](mailto:jabber:ro.franchini@gmail.com) skype:ro.franchini

---

<div class="post-metadata">

**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:** [August 9, 2011, 4:53pm UTC](https://discuss.elastic.co/t/modularization-of-elastic-search-on-maven-central/5070/4 "2011-08-09T16:53:09Z")

</div>

It will require a lot of effort, and will not reduce the size by much...

On Tue, Aug 9, 2011 at 7:45 PM, Roberto Franchini [franchini@celi.it](mailto:franchini@celi.it) wrote:

> On Fri, Aug 5, 2011 at 9:36 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:  
> [cut]
> 
> > So, to answer your question, no, there won't be a smaller jar file in the  
> > future.
> 
> ## Hi, I'm evaluating ES. I understand your needs, but could you split the client part of the jar from the server part? Is it possible to do that without a lot of effort? Cheers, RF
> 
> Roberto Franchini  
> L'impossibile è inevitabile.  
> [http://www.celi.it](http://www.celi.it)  
> [http://www.blogmeter.it](http://www.blogmeter.it)  
> Tel +39.011.562.71.15  
> [jabber:ro.franchini@gmail.com](mailto:jabber:ro.franchini@gmail.com) skype:ro.franchini

---

<div class="post-metadata">

**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, 3:57am UTC](https://discuss.elastic.co/t/modularization-of-elastic-search-on-maven-central/5070/5 "2017-07-06T03:57:43Z")

</div>


