#36745: native support for database connection pooling in Django.
-------------------------------------+-------------------------------------
Reporter: Pravin | Owner: Pravin
Type: New | Status: assigned
feature |
Component: Database | Version: 5.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
In Django, {{{CONN_MAX_AGE }}} helps with persistent connections, but it
doesn’t provide true connection pooling like you’d get with
{{{SQLAlchemy}}} in {{{FastAPI}}} or similar frameworks.
In contrast, SQLAlchemy gives you:
- Configurable pool sizes
- Queueing and timeout behavior
- Recycle/reconnect logic
- Pool health insights
This makes a huge performance difference for apps with high concurrency,
short-lived processes (e.g. in serverless), or async workflows.
--
Ticket URL: <https://code.djangoproject.com/ticket/36745>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019a9bd3b577-f67d3bb8-baeb-4147-a40d-6bc982639972-000000%40eu-central-1.amazonses.com.
