Implement database connection multiplexing for serverless environments

[Smartdevs17]

Context

Serverless functions (webhook handlers, auth callbacks, scheduled jobs) create a new database connection on each invocation, exhausting connection limits during traffic spikes.

Current Limitation/Problem

During traffic spikes, serverless functions open 100+ simultaneous database connections, hitting the 200-connection limit and causing connection refused errors.

Expected Outcome

Database connection multiplexing via PgBouncer (or RDS Proxy), with transaction-level pooling and automatic scaling for serverless workloads.

Acceptance Criteria

• PgBouncer deployment as sidecar container or RDS Proxy configuration
• Transaction pooling mode: connections reused across function invocations
• Prepared statement support: PgBouncer in prepared-statement mode with statement cache
• Authentication: IAM-based (AWS RDS) or SCRAM-256 (self-hosted)
• Connection limits: max 50 pooled connections serving 500+ concurrent functions
• Lambda handler adaptation: db.release() called after each invocation via finally block
• Edge case: connection leak detection (abandoned connection >30s, log and force-close)

Technical Scope

• infra/terraform/ - PgBouncer or RDS Proxy resource provisioning
• backend/shared/db/ - serverless connection pool adapter
• backend/serverless/ - Lambda function database configuration
• docker-compose.yml - local PgBouncer service for development
• backend/monitoring/ - connection pool metrics and leak detection

[jadonamite]

@jadonamite has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer can i work on this issue I have read your requirements and i am ready to jump on this and send out the fix for your review ASAP

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jadonamite to this issue.

[od-hunter]

@od-hunter has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, can I be assigned this issue please? I’ve gone through the issue carefully and I’m up for the task, kindly assign me please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @od-hunter to this issue.

[drips-wave]

Congratulations, @jadonamite! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @jadonamite: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊