kingshard vs PgDog
kingshard
github.com
PgDog
pgdog.devSide by side
| Figure | kingshard | PgDog |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 2 |
| Spec score · Database Proxy Software | 7.4 (#20) | 7.7 (#12) |
| Deployment | The documented installation uses Go, Git clone, make, a YAML configuration file, and a locally run kingshard binary. | PgDog can be deployed with Kubernetes Helm, Docker, AWS ECS Terraform, pre-built binaries, or from source. |
| License | The repository says kingshard is licensed under Apache 2.0. | The project is free and open source under AGPL-3.0, and the documentation says internal use does not require sharing source code. |
| Sharding | It supports hash, range, and date sharding across multiple nodes, as well as sending SQL to a specified node. | PgDog routes queries using sharding keys and can execute queries without a key across databases in parallel. |
Plans
In their own words
PgDog
PgDog is a PostgreSQL connection pooler, load balancer, and database sharder designed to scale databases without application changes. It multiplexes many application connections across fewer PostgreSQL server connections and supports SET, LISTEN/NOTIFY, and advisory locks. Read queries can be distributed across replicas while writes go to the primary, with health checks and failover detection. Sharding keys guide query routing; queries without a key can run across databases in parallel. Cross-shard transactions use PostgreSQL prepared transactions and two-phase commit, with automatic rollback on errors. PgDog can copy data and stream row changes to another database without pausing query traffic. Deployment options include Kubernetes Helm, Docker, AWS ECS Terraform, pre-built binaries, and source. Releases include Linux arm64 and amd64, Apple Silicon Mac, and Debian packages; the macOS binary is unsigned. The project is free and open source under AGPL-3.0, and documentation says internal use does not require sharing source code. Enterprise support includes architecture reviews, a dedicated Slack channel, and an SLA promising a response within 15 minutes.