# Why had Elastic released a complete new API with 8.0? **URL:** \ **Category:** Elasticsearch\ **Tags:** language-clients\ **Created:** [October 24, 2022, 4:01am UTC](https://discuss.elastic.co/t/why-had-elastic-released-a-complete-new-api-with-8-0/317292 "2022-10-24T04:01:59Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Michael\_Gattinger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_gattinger/32/99690_2.png) [@Michael\_Gattinger](https://discuss.elastic.co/u/Michael_Gattinger)\ **Post date:** [October 24, 2022, 4:02am UTC](https://discuss.elastic.co/t/why-had-elastic-released-a-complete-new-api-with-8-0/317292/1 "2022-10-24T04:02:00Z")
Why had Elastic released a complete new API with 8.0? High Level API Client was working well. Why replacing it with Elasticsearch Java API Client? Thanks - Enomine ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 24, 2022, 6:12am UTC](https://discuss.elastic.co/t/why-had-elastic-released-a-complete-new-api-with-8-0/317292/2 "2022-10-24T06:12:48Z")
Mainly because the old client was using internal classes from the Elasticsearch server and was coupled with it. As a consequence: - the "client jar" was as fat as the server - it was depending on Lucene which was sometimes leading to jar conflicts - you must have the same version between the server and the client - was harder to maintain as there was no real contract for the APIs The new one is coming with so many benefits. To name a few: - you can use your business objects directly instead of doing the serialization manually and you can directly get your business objects from the responses. - compatibility with reactive patterns - fluent API - less risks of breaking the client when a refactoring is happening on the server side ---
**Author:** ![Michael\_Gattinger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_gattinger/32/99690_2.png) [@Michael\_Gattinger](https://discuss.elastic.co/u/Michael_Gattinger)\ **Post date:** [October 30, 2022, 10:19pm UTC](https://discuss.elastic.co/t/why-had-elastic-released-a-complete-new-api-with-8-0/317292/3 "2022-10-30T22:19:17Z")
Thanks for that information. Here i have an additional question... > **[Overview | Java REST Client \[7.17\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/java-rest/current/java-rest-overview.html)** -\> Elasticsearch Version 7 had a "Java REST Client", which included a "Java Low Level REST Client" as well as a "Java High Level REST Client". > **[Elasticsearch Java API Client \[8.4\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/index.html)** > **[Java Low Level REST Client | Elasticsearch Java API Client \[8.4\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/java-rest-low.html)** -\> Elasticsearch Version 8 has a "Elasticsearch Java API Client", which includes a "Java Low Level REST Client". Elasticsearch Java API Client seem to be the counterpart of the Java High Level REST Client. Question: **Is the Java Low Level REST Client in ESJAC technicaly the same (is it a copy of the same code) as the Java Low Level REST Client from Java REST Client? Or was it rewritten, too?** Thanks - Enomine ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 30, 2022, 10:54pm UTC](https://discuss.elastic.co/t/why-had-elastic-released-a-complete-new-api-with-8-0/317292/4 "2022-10-30T22:54:28Z")
The Low Level Client is the same for both High Level clients. ---
**Author:** ![Michael\_Gattinger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_gattinger/32/99690_2.png) [@Michael\_Gattinger](https://discuss.elastic.co/u/Michael_Gattinger)\ **Post date:** [October 31, 2022, 1:44am UTC](https://discuss.elastic.co/t/why-had-elastic-released-a-complete-new-api-with-8-0/317292/5 "2022-10-31T01:44:50Z")
Thanks - Enomine ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 28, 2022, 1:45am UTC](https://discuss.elastic.co/t/why-had-elastic-released-a-complete-new-api-with-8-0/317292/6 "2022-11-28T01:45:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.