Share one PostgreSQL pool across FastAPI services with schema-isolated managers.
npx skills add https://github.com/juanre/pgdbm --skill shared-pool-pattern
Please help me install this Agent Skill. Skill: shared-pool-pattern Source: https://github.com/juanre/pgdbm/tree/main/skills/shared-pool-pattern Command: npx skills add https://github.com/juanre/pgdbm --skill shared-pool-pattern
This Skill provides a proven pattern for sharing a single database connection pool across multiple services within a single application, reducing resource usage and connection overhead while preserving service isolation.
Initialize a shared pool at application startup, then create per-service managers with distinct schemas and run migrations.
High-intent search queries and answers about installing and using this skill.
Create a shared pool at application startup using create_shared_pool, then instantiate per-service AsyncDatabaseManager instances with distinct schemas. Each service reuses the single pool while maintaining isolation through dedicated database schemas, reducing connection overhead across your multi-service app.
Yes. Assign unique module_names to each service's AsyncDatabaseManager so migrations run per-service schema without conflicts. This pattern lets you maintain separate migration histories and schemas while sharing the underlying connection pool.
Schema isolation separates tables by service within a single database. Each AsyncDatabaseManager gets its own schema, preventing table name collisions and keeping services independent while benefiting from a shared pool's resource efficiency.
Initialize the shared pool during FastAPI startup via lifespan context managers, then inject per-service managers through FastAPI dependencies. This ensures proper pool creation, cleanup, and availability across all service endpoints.
Yes. The pattern uses AsyncDatabaseManager instances designed for async workflows, integrating seamlessly with FastAPI's async/await model and lifespan management for non-blocking database access across services.
A shared pool reduces total connection count to the database, lowering memory overhead and connection limits strain. Instead of each service maintaining its own pool, all services reuse connections from one pool, improving resource utilization in multi-service deployments.
agusmdevGenerate FastAPI backend entity modules with models, schemas, and routers.
eng-vmessiahProvide relational database design patterns for schema migrations, indexing, and query optimization.
ruskibeatsModify alembic/env.py to replace async SQLAlchemy operations with sync versions.
raphaelmansuyImplement multi-tenant PostgreSQL isolation with row-level security.
