EOL.Wiki EOL.Wiki
← ← Back to all products

Apache ShardingSphere

Active
Middleware Latest Version: 5.5.3 Latest Release: Feb 28, 2026

Apache ShardingSphere is an open-source distributed database ecosystem providing data sharding, read/write splitting, encryption, and a database-plus architecture via JDBC and Proxy.

Versions

8

Latest Version

5.5.3

Active Support

1

EOL

7

Lifecycle Timeline

Today
5.5
5.5
5.4
5.4
5.3
5.3
5.2
5.2
5.1
5.1
5.0
5.0
4.1
4.1
4.0
4.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.5Apr 30, 2024YesNo5.5.3No
Active
5.4Jul 8, 2023NoYes5.4.1No
EOL
5.3Jan 8, 2023NoYes5.3.2No
EOL
5.2Sep 8, 2022NoYes5.2.1No
EOL
5.1Feb 16, 2022NoYes5.1.2No
EOL
5.0Nov 10, 2021NoYes5.0.0No
EOL
4.1May 21, 2020NoYes4.1.1No
EOL
4.0Jan 13, 2020NoYes4.0.1No
EOL

Frequently Asked Questions

Which versions of Apache ShardingSphere have reached end of life?
The following Apache ShardingSphere versions have reached end of life and no longer receive security updates: 5.4, 5.3, 5.2, 5.1, 5.0, 4.1, 4.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache ShardingSphere 5.4?
Apache ShardingSphere 5.4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache ShardingSphere?
The latest version of Apache ShardingSphere is 5.5.3, released in the 5.5 release cycle.
How many versions of Apache ShardingSphere are currently supported?
Apache ShardingSphere currently has 1 actively supported version(s): 5.5.
When does Apache ShardingSphere 5.5 reach end of life?
Apache ShardingSphere 5.5 does not have a specific end-of-life date announced yet.
What should I do when Apache ShardingSphere reaches end of life?
When a Apache ShardingSphere version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.