What is the difference between this and pgbouncer / other connection pooling alternatives?

[YPCrumble]

This is an interesting library as it seems easier to implement than pgbouncer. A section in the README explaining the difference between this and pgbouncer and potentially other libraries would be really helpful.

[jkgenser]

This is an in-process connection pool. It uses sqlalchemy's connection pool.

pgbouncer is a standalone proxy. It can be deployed as a sidecar to a process and function as a pooler for a process which would have a similar effect as this library.

pgbouncer can also be deployed as a proxy that receives n connections, and process/app level pooling would not be needed in such a scenario

[altairbow]

django-db-connection-pool is a wrapper based on SQLAlchemy connection pool, designed based on Django database connection backend, It is a easy way to implement connection pooling for multiple database types in Django.

PgBouncer has an independent connection pool implementation and cannot be used directly in Django