Start here
Evaluate DBProxy and run a safe first deployment.
Rust data-plane proxy · pre-1.0
One hop.
Explicit decisions.
Route MySQL, PostgreSQL/TimescaleDB, and Redis/Valkey traffic across pools and shards while keeping failure boundaries visible.
- ProtocolsMySQL · PostgreSQL · RESP
- Routingread/write · hash · range · value
- Modelindependent data-plane replicas
routing decision
op_7J2k…mQ
Example routing decisions
requestSELECT … tenant_id = 11
AST key
dbproxy decisionread · shard 01
healthy
destinationorders-1 / replica-b
Documentation paths
Start with the decision you need to make.
Route traffic
Choose protocol modes, pools, shards, and topology behavior.
Protect data
Define cache, transaction, fanout, and runtime-policy contracts.
Operate
Monitor limits, readiness, failure modes, and open boundaries.
Protocol modes
Preserve the wire, or terminate it for control.
Statement-aware by default
Terminate the protocol for SQL parsing, prepared routing, pooled backends, cache policy, and XA fanout.
Read the architecture →Choose fidelity or pooling
Use transparent relay for full protocol fidelity, or transaction mode for bounded pools and statement routing.
Compare the modes →Pin a connection or route keys
Keep RESP transparent, or use command mode for CRC16 placement and guarded multi-key operations.
Choose a topology →Production contract
Uncertainty does not become a replica read or a cross-shard guess.
Unsupported SQL shapes, topology ambiguity, metadata mismatch, and unsafe distributed operations fail closed. The boundary pages state what DBProxy can prove today.
Local demo
Three commands to a routed stack.
./deploy.sh
./scripts/smoke.sh
./deploy.sh local-down