This is the second annual Django Developers Survey, conducted September – October, 2022, as a collaborative effort between the Django Software Foundation and JetBrains. To help us get a better idea of the current state of the framework and the ecosystem around it, 4,900 Django users and enthusiasts from 248 countries and regions took the survey.
The majority of users migrated to the latest version 4.1 but almost half of Django developers still rely on the 3.2 LTS version.
Django versions 3.1 and lower are used by experienced Python developers, while newcomers use only the newest versions.
Django developers usually upgrade their projects with either every stable release (44%) or only with long-term support (LTS) (32%).
Django officially supports the following databases: PostgreSQL, SQLite, MySQL, MariaDB, and Oracle. Since last year’s survey, PostgreSQL has become even more popular, with shares increasing by 2 percentage points.
Only 6% of developers use databases that are not supported by Django. The database mentioned most often by these developers is MongoDB.
Practiced by more than half of Django developers, caching with Redis is the most popular.
Developers who use Redis as a cache backend use TypeScript more often than those who choose other caching methods.
PostgreSQL database users prefer Redis and Memcached.
Among SQLite users, the biggest share is Filesystem, with local memory being the second most popular.
The use of GeoDjango backend highly correlates with the choice of database backend.
More than 80% of respondents chose admin or auth, which makes them the most popular contrib apps for the second year in a row.
The favorite core component among respondents is Models. It was chosen by 76% of Django users, which is 4 percentage points higher than the previous year.
Compared to last year's results, the share of jQuery decreased by 5 percentage points.
It’s interesting to note that frameworks that used to be leaders are beginning to lose their share to newly emerging ones.
Half of Django developers write asynchronous (async) views. However, whether or not respondents use async technologies does not necessarily correlate with their developer experience.
Check out more about Django asynchronous support here.
The more experienced developers use type hints significantly more often than those developers with less experience. Overall, 46% of Django developers use type hints.
Bigger teams are more likely to document software, such as on Github Pages which is mostly used by bigger teams.
Smaller teams publish documentation less often.
This question was only shown to those who chose Python as a secondary language.
The biggest users of YouTube and Stack Overflow are developers who have worked for less than 2 years.
Those with 6 or more years of work experience almost never use YouTube for Django learning purposes. They typically read djangoproject.com and Django News.
According to the official Python Developers Survey, Django developers prefer to use the newest Python versions more often than Python developers in general. This is particularly the case with the usage of version 3.9, which is 29 percentage points higher with Django (51%) than with Python in general (22%).
Developers who visit python.org tend to upgrade Python to every stable release more often than those who use OS-provided Python.
Developers located in Asia prefer using python.org twice as much as developers in general (27% vs 13%), while those located in Europe choose OS-provided Python 22 percentage points more (55% vs. 33%).
There has been a 6 percentage point rise in Poetry’s share from 13% in 2021 to 19% by the end of 2022.
The share of Black code formatter has significantly increased (by 16 percentage points) when compared with last year’s survey results.
Psycopg2 and Requests are the most used Python packages among Django users, each with 54%.
Requests is a popular platform among all Python developers, while Psycopg2 seems to be Django-specific.
Pillow, a module for working with images, is popular with less experienced developers.
With 56% share, AWS is usually the choice for developers from North and Central America.
Heroku is leading in Africa with 39% share, whereas AWS is a close second with 37%.
Furthermore, PythonAnywhere has higher demand in Africa and the Middle East with 20% share, and in Asia it has 19%. In all other parts of the world it has less than 10%.
Since last year, the share of GitHub Actions has increased slightly by 7 percentage points, while Jenkins and Travis CI have lost 2 and 4 percentage points respectively.
The use of Docker containers for backing services and utilities is lower for individuals and small companies with fewer than 10 people.
45% of developers with 11 or more years of experience debug their applications using shell / pdb, while only 20% of developers with less than 1 year’s experience and 30% of developers with 1–2 years’ experience do so.
Django users freelance at twice the rate of developers in general: the share of freelancers in this survey is 11%, compared with just 5% in the total developer ecosystem and 6% in the Python Developers Survey.
This year’s demographics show that the 2022 survey respondents are slightly more experienced than last year’s.
Django developers tend to work in small teams.
The more experienced the developer, the more projects they tend to have. Developers with less experience generally work on one main project with several side projects, or even on a single main project.
Want to dig further into the data? Download the anonymized survey responses and see what you can learn! Share your findings and insights by mentioning @jetbrains and @djangoproject on Twitter with the hashtag #djangosurvey.
The data set includes responses only from official Django Software Foundation channels. After filtering out duplicate and unreliable responses, the data set includes around 4,900 responses collected in September – October, 2022 through the promotion of the survey on official Django channels, such as djangoproject.com and the DSF's Twitter account. In order to prevent the survey from being slanted in favor of any specific tool or technology, no product-, service-, or vendor-related channels were used to collect responses.
The data are anonymized, with no personal information or geolocation details. Moreover, to prevent the identification of any individual respondents by their verbatim comments, all open-ended fields have been deleted.
To help you better understand the logic of the survey, we are sharing the data set, the survey questions, and all the survey logic.
Once again, on behalf of both the Django Software Foundation and JetBrains, we’d like to thank everyone who took part in this survey.