# Elasticsearch and Guice

**URL:** <https://discuss.elastic.co/t/elasticsearch-and-guice/246712>\
**Category:** Elasticsearch\
**Created:** [August 28, 2020, 4:21am UTC](https://discuss.elastic.co/t/elasticsearch-and-guice/246712 "2020-08-28T04:21:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhargavkn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargavkn/32/75411_2.png) [@bhargavkn](https://discuss.elastic.co/u/bhargavkn)\
**Post date:** [August 28, 2020, 4:21am UTC](https://discuss.elastic.co/t/elasticsearch-and-guice/246712/1 "2020-08-28T04:21:53Z")

</div>

Hi,  
I was recently going through elasticsearch's [codebase](https://github.com/elastic/elasticsearch) and saw that a using a fork of Guice is being used for dependency injection. With a little more search on the internet ([here](https://github.com/elastic/elasticsearch/issues/43881), and [here](https://discuss.elastic.co/t/elasticsearch-and-guice/57822)), it seems that there are efforts being put in to remove Guice from elasticsearch. I wanted to know more about the reasons that led to this effort? I can understand that maintaining a fork of Guice has led to updates being missed from the main branch, but if that was the main reason and there were no other issues with Guice, then the effort would have been to migrate Elasticsearch to use the latest version of Guice. Also, if the plan is to move away from Guice for dependency injection, what's the replacement that you're planning to use?

---

<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:** [September 25, 2020, 4:21am UTC](https://discuss.elastic.co/t/elasticsearch-and-guice/246712/2 "2020-09-25T04:21:55Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.