rds-auth-proxy
pgbouncer
| rds-auth-proxy | pgbouncer | |
|---|---|---|
| 1 | 34 | |
| 34 | 2,680 | |
| - | 2.6% | |
| 2.4 | 8.7 | |
| 2 months ago | 6 days ago | |
| Go | C | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rds-auth-proxy
pgbouncer
-
MongoDB and Load Balancer Support
Thanks to MongoDB drivers all consistently providing connection monitoring and pooling functionality, external connection pooling solutions aren't required (ex: Pgpool, PgBouncer). This allows applications built using MongoDB drivers to be resilient and scalable out of the box, but based on what we understand regarding the number of connections applications establish to MongoDB clusters it stands to reason that at a certain point as our application deployments increase, so will our connections.
-
Minha jornada de otimização de uma aplicação django
Pgbouncer - resolvia o problema do limite de conexões no postgres. Mas a API “saudável” manteve o número de conexões baixo o suficiente.
- PgBouncer 1.21.0 – "The one with prepared statements"
- Pgbouncer adds support for prepared statements
-
PgBouncer is useful, important, and fraught with peril
Pgbouncer maintainer here. Overall I think this is a great description of the tradeoffs that PgBouncer brings and how to work around/manage them. I'm actively working on fixing quite a few of the issues in this blog though
1. Named protocol-level prepared statements in transaction mode has a PR that's pretty close to being merged: https://github.com/pgbouncer/pgbouncer/pull/845
-
Supavisor: Scaling Postgres to 1 Million Connections
A common solution is connection pooling. Supabase currently offers pgbouncer which is single-threaded, making it difficult to scale. We've seen some novel ways to scale pgbouncer, but we have a few other goals in mind for our platform.
-
Citus 12: Schema-based sharding for PostgreSQL
Great observation! :)
We worked upstream to have `search_path` properly handled (tracked per client) by pgbouncer.
https://github.com/pgbouncer/pgbouncer/commit/8c18fc4d213ad4...
Check config.md in that commit for a verbose, humanized description.
What are some alternatives?
authentik - The authentication glue you need.
odyssey - Scalable PostgreSQL connection pooler
introspector - A schema and set of tools for using SQL to query cloud infrastructure.
asyncpg - A fast PostgreSQL Database Client Library for Python/asyncio.
iamzero - Identity & Access Management simplified and secure.
pgcat - PostgreSQL pooler with sharding, load balancing and failover support. [Moved to: https://github.com/postgresml/pgcat]
zitadel - Cloud-native Identity & Access Management solution providing a platform for secure authentication, authorization and identity management.
TimescaleDB - An open-source time-series SQL database optimized for fast ingest and complex queries. Packaged as a PostgreSQL extension.
rds_iamauth_proxy - Postgres proxy which allows tools that don't natively supports IAM auth to connect to AWS RDS instances.
pgcat - PostgreSQL pooler with sharding, load balancing and failover support.
citus - Distributed PostgreSQL as an extension
pg_bulkload - High speed data loading utility for PostgreSQL