HeliosProxy vs PgBouncer

HeliosProxy is a self-hosted, programmable PostgreSQL data-plane for routing connections, handling failover, replaying traffic, and supporting database upgrades. It provides session, transaction, and statement pooling, with multiplexing up to 100:1. Routing can account for replica lag, workload type, and failing backends through circuit breaking. Cache options include local memory, Redis-backed storage, and semantic tiers, with invalidation when writes occur. Transaction Replay can move sessions to a new primary and optionally replay reads or transactions when conditions permit, although prepared statements, temporary tables, open cursors, advisory locks, and extended-protocol SET statements are not restored. A WebAssembly plugin runtime offers five hook points, Ed25519 verification, and OCI distribution. The admin console includes topology, plugin, chaos, shadow-execution, and traffic-replay panels. Authentication supports JWT, OAuth 2.0, LDAP, and API keys. HeliosProxy works with PostgreSQL 12+ and compatible databases, and deployment documentation covers Docker, Kubernetes, and standalone setups. It is open source under Apache 2.0 and costs nothing.

PgBouncer is a self-hosted connection pooler for PostgreSQL. It reuses server connections to lessen the performance cost of opening new ones, and offers session, transaction, and statement pooling. Statement pooling does not allow multi-statement transactions. PgBouncer can send connections to databases on different hosts, but it has no built-in multi-host load balancing or failover detection; DNS round-robin, external TCP load balancers, DNS changes, or external tools are described as alternatives. It can track protocol-level prepared statements in transaction and statement modes when max_prepared_statements is non-zero. Authentication options include client certificates, SCRAM-SHA-256, LDAP, PAM, and HBA-based configuration. The features page lists default memory needs of 2 kB per connection. PgBouncer is free, with source releases and references to native packages and RPM and Debian repositories. It runs on Linux and Windows; MinGW is the documented supported Windows build environment. Building requires Libevent 2.0 or later, pkg-config, and a C11-capable compiler; TLS support also requires OpenSSL.