# apache/shardingsphere

Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.

Repository: https://github.com/apache/shardingsphere
Canonical: https://ross.abutalabs.com/products/shardingsphere
Language: Java
License: Apache-2.0
License Family: permissive
Topics: database, distributed-database, distributed-sql-database, sql, shard, database-cluster, mysql, postgresql, encrypt, bigdata, data-encryption, data-pipeline, database-middleware, distributed-transaction, read-write-splitting, database-gateway
Last push: 2026-08-26T00:21:24+00:00

## Health v2 (maintenance only)
Score: 79/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 40, longevity 100
- inputs: {"age_days": 3880, "days_push": 8, "days_rel": 186, "gap_med": 247.0, "n_releases_24m": 3}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 20788, forks 6907 (observed 2026-08-28T04:11:30.411959+00:00)

## What it is
Apache ShardingSphere is an enterprise distributed database ecosystem that turns heterogeneous databases (MySQL, PostgreSQL, etc.) into a distributed SQL system with sharding, read-write splitting, encryption, and distributed transactions. It can be deployed as a JDBC driver, a proxy gateway, or embedded sidecar.

## Use cases
- shard a large MySQL table across multiple database nodes
- add read-write splitting to scale database reads
- transparently encrypt sensitive database columns
- run distributed transactions across multiple databases
- put a SQL gateway in front of heterogeneous databases
- scale PostgreSQL horizontally without rewriting application SQL

## When to choose
- you need horizontal database scaling via sharding without changing application code
- you want transparent data encryption or masking at the database layer
- you need read-write splitting or distributed transactions across existing MySQL/PostgreSQL instances

## When to avoid
- your dataset fits comfortably in a single database instance
- you need a fully managed distributed SQL database rather than middleware over existing databases
- your stack is not JVM/SQL-based

## Facets
- artifact type: framework
- maturity: stable
- function: database, database-driver, security, cryptography, api-gateway, microservices, middleware
- domain: databases, microservices, big-data, security, backend
- platform: jvm, cloud, self-hosted, cross-platform
- tags: sharding, read-write-splitting, distributed-sql, database-middleware, data-encryption, distributed-transactions, database-gateway, federation, apache, data-engineering, docker, kubernetes

## Member repositories
- apache/shardingsphere (main) score 79

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:30.411959+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T16:58:32.953805+00:00, confidence not recorded.
  - readme: https://github.com/apache/shardingsphere (fetched 2026-08-28T04:11:30.411959+00:00, sha 5cb7d5d3e1a4)
- Data as of 2026-08-30T08:39:29.467469+00:00.