A · leads
etcd
97.9
52,615 stars · Apache-2.0
Databases
etcd leads by 3.5 · narrow
A · leads
97.9
52,615 stars · Apache-2.0
B
94.4
20,830 stars · Apache-2.0
etcd versus shardingsphere is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. etcd is written mainly in Go; shardingsphere is written mainly in Java. The composite score is 97.9 for etcd and 94.4 for shardingsphere.
etcd has 52,615 GitHub stars to shardingsphere's 20,830, a gap of 31,785 (2.53×). Forks are 10,608 for etcd and 6,910 for shardingsphere. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 95.
Push history: etcd was last pushed on 17 November 2026 (0 days ago), and shardingsphere was last pushed on 17 November 2026 (0 days ago). Open issues stand at 478 for etcd (0.009 per star) and 267 for shardingsphere (0.013 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both etcd and shardingsphere are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both etcd (52,615 stars) and shardingsphere (20,830 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: etcd is open source, shardingsphere is open source.
etcd is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is adoption at 8 points (100 vs 92), and the tightest is self-hosting at 0 points (100 vs 100).
etcd finishes ahead at 97.9 against shardingsphere at 94.4, a 3.5 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | etcd | shardingsphere |
|---|---|---|
| GitHub stars | 52,615 | 20,830 |
| Forks | 10,608 | 6,910 |
| Open issues | 478 | 267 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 94.4 |
Distributed reliable key-value store for the most critical data of a distributed system
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
etcd has more GitHub stars: 52,615 versus 20,830 for shardingsphere. The gap is 31,785 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both etcd and shardingsphere as self-hostable. Confirm each project's deploy docs before you plan a migration.
etcd is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. shardingsphere is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
etcd scores 97.9 and shardingsphere scores 94.4. This page calls that a narrow lead for etcd.