Alternatives to TiCDC

It suits teams that need a distributed database for transactional, analytical, and AI workloads, especially where Oracle or MySQL compatibility matters.

DBLE

DBLE is intended for teams replacing or scaling a single MySQL instance as workloads grow.

HeliosProxy

HeliosProxy suits teams running PostgreSQL-compatible databases that need self-hosted pooling, routing, caching, and failover controls.

SPQR is intended for PostgreSQL developers who want to avoid implementing sharding logic in their applications, especially for workloads suited to single-shard OLTP queries.

Heimdall Database Proxy

It may suit teams that need SQL routing, caching, pooling, and query visibility between applications and databases.

PgBouncer suits PostgreSQL operators who want to reuse connections and choose among three pooling modes.

PgDog

PgDog suits teams running PostgreSQL that need connection pooling, read distribution, failover detection, or sharding.

It suits Linux teams running their own database infrastructure and needing distributed SQL, routing, pooling or load balancing.

pgagroal suits administrators running self-hosted PostgreSQL who need connection limits, monitoring, credential controls, and failover hooks.

PgCat suits teams operating PostgreSQL who need self-hosted connection pooling, query routing, and failover on Linux.

TurbineProxy suits teams running MySQL or PostgreSQL that want self-hosted query routing and connection pooling.

It suits teams running PostgreSQL 10+ that want self-managed pooling, load balancing, and failover on Linux or macOS.

ShardingSphere-Proxy

It suits teams that need a self-hosted proxy for routing, sharding, or distributed transactions across databases.

Pgpool-II

It suits PostgreSQL administrators who need self-hosted pooling, query routing, replication, or failover middleware.

ProxySQL

It suits teams running self-hosted Linux database infrastructure that need pooling, routing, caching or failover.

This proxy suits teams running supported TencentDB for MySQL deployments that need routing, pooling, load balancing, monitoring, and failover.