Database Proxies & Query-Optimization Middleware
Parent: Software Engineering Patterns · Topic entry · 15 branches · skill distributed-systems-and-datastores/references/database-proxies-query-middleware
A published reference is not available for this topic yet.
Children
- Connection pooling & multiplexing (frontier)
- Read/write splitting & replica routing (frontier)
- Read-after-write / replication-lag staleness hazard (causal_reads, GTID sync) (frontier)
- Proxy query result caching (TTL vs invalidation) (frontier)
- Query rewriting & SQL firewall (digest allow-list) (frontier)
- Proxy-based sharding / horizontal scale-out (Vitess vtgate) (frontier)
- Failover acceleration & proxy-tier HA (SPOF, sidecar vs centralized vs Keepalived) (frontier)
- Credential brokering (IAM / Secrets Manager) (frontier)
- Proxy-vs-driver-vs-app decision framework & pool sizing (frontier)
- ProxySQL (frontier)
- MariaDB MaxScale (frontier)
- PgBouncer (frontier)
- PgCat & Pgpool-II (frontier)
- AWS RDS Proxy (frontier)
- mongos as MongoDB's native router & why MongoDB rarely uses third-party proxies (frontier)
Frontier under this node: AWS RDS Proxy, Connection pooling & multiplexing, Credential brokering (IAM / Secrets Manager), Failover acceleration & proxy-tier HA (SPOF, sidecar vs centralized vs Keepalived), MariaDB MaxScale, PgBouncer, PgCat & Pgpool-II, Proxy query result caching (TTL vs invalidation), Proxy-based sharding / horizontal scale-out (Vitess vtgate), Proxy-vs-driver-vs-app decision framework & pool sizing, ProxySQL, Query rewriting & SQL firewall (digest allow-list), Read-after-write / replication-lag staleness hazard (causal_reads, GTID sync), Read/write splitting & replica routing, mongos as MongoDB's native router & why MongoDB rarely uses third-party proxies