# polardb/polardbx-sql

PolarDB-X is a cloud native distributed SQL Database designed for high concurrency, massive storage, complex querying scenarios.

Repository: https://github.com/polardb/polardbx-sql
Canonical: https://ross.abutalabs.com/products/polardbx-sql
Language: Java
License: Apache-2.0
License Family: permissive
Topics: horizontal-scaling, distributed-transactions, htap, enterprise-class, cloud-native, high-availability, mysql, high-concurrency, massive-datasets, relational-database
Last push: 2025-12-05T09:19:33+00:00

## Health v2 (maintenance only)
Score: 49/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 55, release rhythm 12, longevity 100
- inputs: {"age_days": 1782, "days_push": 271, "days_rel": 376, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1682, forks 338 (observed 2026-08-28T04:05:21.702372+00:00)

## What it is
PolarDB-X is a cloud native distributed SQL database built in Java with a shared-nothing architecture that decouples compute from storage. It provides transparent horizontal scaling, ACID distributed transactions, HTAP workloads, and high MySQL compatibility, battle-tested on Alibaba's core transaction systems.

## Use cases
- scale a MySQL-compatible database horizontally beyond a single node
- run distributed transactions with ACID guarantees across shards
- run mixed OLTP and OLAP workloads on one database
- handle massive datasets with high concurrency like flash-sale traffic
- deploy a highly available database across data centers with Multi-Paxos replication
- migrate existing MySQL applications to a distributed database with minimal changes
- manage database clusters on Kubernetes via an operator

## When to choose
- you need MySQL compatibility but outgrow single-node capacity or throughput
- you require distributed transactions and strong consistency across shards
- you want HTAP capabilities combining transactional and analytical queries
- you need enterprise features like TDE, SQL concurrency control, and flashback query
- you deploy on Kubernetes or want public, private, or hybrid cloud options

## When to avoid
- your workload fits comfortably on a single MySQL or PostgreSQL instance
- you need a fully managed database without operating your own cluster
- you depend on non-MySQL databases or exotic SQL dialects
- your team cannot operate a distributed Java-based database system
- you need a lightweight embedded or edge database

## Facets
- artifact type: service
- maturity: stable
- function: database, search-engine, caching
- domain: databases, microservices, cloud-computing, big-data, analytics
- platform: cloud, self-hosted, jvm
- tags: distributed-sql, mysql-compatible, horizontal-scaling, distributed-transactions, htap, shared-nothing, sharding, high-availability, multi-paxos, mpp, linux, docker, kubernetes

## Member repositories
- polardb/polardbx-sql (main) score 49

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:21.702372+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-30T03:41:23.211567+00:00, confidence not recorded.
  - readme: https://github.com/polardb/polardbx-sql (fetched 2026-08-28T04:05:21.702372+00:00, sha fc4d1465da2b)
- Data as of 2026-08-30T08:39:29.467469+00:00.