Azure Cosmos DB's Java SDK v3.x is retiring on 31 August 2024

[azure-deprecation-automation]

Azure Cosmos DB's Java SDK v3.x is retiring on 31 August 2024

Deadline: Aug 31, 2024 Impacted Services:

• Azure Cosmos Db

More information:

• https://azure.microsoft.com/en-au/updates/retirement-notice-update-java-sdk-3x-to-java-sdk-4x-by-31-august-2024/
• https://docs.microsoft.com/en-us/azure/cosmos-db/migrate-java-v4-sdk?tabs=java-v4-async

Notice

Here's the official report from Microsoft:

Because Azure Cosmos DB Java SDK v4 has up to 20% enhanced throughput, TCP-based direct mode, bug fixes, and provide support for the latest backend features, we’ll retire 3.x version of the Azure Cosmos DB Java SDK for SQL API on 31 August 2024. We recommend you make the switch early to gain the enhanced benefits of Azure Cosmos DB Java SDK 4.x. Start using SDK 4.x for net-new subscriptions/accounts.

In addition to current features you already use, here’s a quick comparison between Azure Cosmos DB Java SDK 3.x and Azure Cosmos DB Java SDK 4.x:

Java SDK 3.x	Java SDK 4.x
- HTTP-based direct mode	- ~20% improved throughput with TCP
- Manual throughput mode only	- All modes including autoscale supported

After 31 August 2024, if you prefer not to upgrade, requests sent from 3.x SDK will continue to be served by the Azure Cosmos DB service. No further updates will be made for 3.x version of the Azure Cosmos DB Java SDK for SQL API.

Timeline

Phase	Date	Description
Announcement	Aug 17, 2021	Deprecation was announced
Deprecation	Aug 31, 2024	It will keep on working, but no further updates will be made for 3.x version of the Azure Cosmos DB Java SDK for SQL API.

Impact

Azure Cosmos DB's Java SDK v3.x will no longer receive patches after 31 August 2024.

Required Action

A migration guide is available in the documentation.

Here's the official report from Microsoft:

Please follow the steps to migrate your application to use the Azure Cosmos DB Java SDK version 4.

Contact

You can get in touch through the following options:

• Get answers from Microsoft Q&A (link).
• Contact Azure support (link).

[azure-deprecation-automation]

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.