nickjj / nickjj/docker-django-example
Connection Pooling for Django Project
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 475
- PR merge metrics
- No merged PRs in 30d
Description
Hi @nickjj, thank you for making this repository. I would have a look at this repo for my reference.
I'm looking for a Django project example that uses connection pooling (pgbouncer or pgpool) but seems like this repo does not use this.
My concern is because Django's DB connection is created during the request and closed after returns the response. this based on the documentation https://docs.djangoproject.com/en/3.2/ref/databases/#general-notes
I think using connection pooling would make this project better for production-ready project reference.
Thank you in advance
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Django database connection lifecycle and the existing Docker Compose services first, then compare the pgbouncer and pgpool options named in the issue. Done should mean the example includes a working production-oriented connection-pooling setup and explains how it is configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, docker, docker-compose, postgres, python
- Domain
- backend, databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100