One of the common problems with Django apps is memory leaks. The most common suggestion is to allow the webserver to cycle processes after serving some fixed number of requests. This bypasses memory issues by just returning used up memory and start fresh.

Perhaps you can consider supporting something similar to gunicorn early in the design.

gunicorn --max-requests 1000 --max-requests-jitter 50 app.wsgi

This is also supported in uwsgi, one of the popular alternatives to gunicorn.
Similar issues are solved in celery worker_max_tasks_per_child since i think it's fairly hard to track down and fix memory issues in larger Python projects with hundreds of dependencies.

References

• https://docs.gunicorn.org/en/latest/settings.html#max-requests
• https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=ma-requests#max-requests
• https://adamj.eu/tech/2019/09/19/working-around-memory-leaks-in-your-django-app/