azure-deprecation / dashboard

Notices about Azure services & features being deprecated
https://azure-deprecation-notices.cloud
MIT License
134 stars 6 forks source link

Sync v2.x of Java SDK for Azure Cosmos DB (SQL API) is retiring on Feb 29, 2024 #142

Open azure-deprecation-automation opened 3 years ago

azure-deprecation-automation commented 3 years ago

Sync v2.x of Java SDK for Azure Cosmos DB (SQL API) is retiring on Feb 29, 2024.

Deadline: Feb 29, 2024 Impacted Services:

More information:

Notice

Here's the official report from Microsoft:

We recently announced the release of Azure Cosmos DB Java SDK v4. This new version of SDK 4 has up to 20% enhanced throughput, TCP-based direct mode, and other performance improvements benefits highlighted in this blog post. With the enhanced capabilities, we retire Sync 2.x version of the Azure Cosmos DB Java SDK for SQL API on 29 February 2024. We recommend you make the switch early to gain the enhanced benefits of Azure Cosmos DB Java SDK v4.

Timeline

Phase Date Description
Announcement Feb 25, 2021 Deprecation was announced
Deprecation Feb 29, 2024 v2 Java SDK will no longer be supported nor patched

Impact

Sync v2.x of Java SDK for Azure Cosmos DB (SQL API) is retiring on 24 May 2021, it is recommended to upgrade to Azure Cosmos DB Java SDK v4.

Required Action

Here's the official report from Microsoft:

Prior to 29 February 2024, all features and functionality currently available for SDK v2.x will be maintained, and no new features will be introduced going forward.

After 29 February 2024, Azure Cosmos DB will no longer make bug fixes, add new features, and provide support to the Sync 2.x version of the Azure Cosmos DB Java SDK for SQL API. If you prefer not to upgrade, requests sent from Sync 2.x of the SDK will continue to be served by the Azure Cosmos DB service.

Please follow the steps below to update your application:

Contact

You can get in touch through the following options:

azure-deprecation-automation commented 3 years ago

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