Django

Backend

Django is a Python framework with a built-in admin panel, ORM and user auth; I know it, though for Python APIs I usually choose FastAPI.

How I use Django

It's aimed at larger web applications with many data models, where a lot comes already solved.

For a client, Django's advantage is an admin panel for entering and reviewing data from day one, with protection against common attacks like CSRF, SQL injection and XSS switched on by default. Its clear project structure also makes it easy for another Django developer to pick up the work.

When working with Django, I define models in Python and track database changes through migrations, tailor the admin to the owner's needs, and add Django REST Framework for APIs. I don't have a portfolio project built on Django, so I count it among the tools I use less often.

In my own projects I usually choose FastAPI for Python APIs, since it's lighter for smaller services and produces API documentation on its own, and I often use Supabase for the database and sign-in. I'd suggest Django for a larger system with many models that needs a ready-made admin panel.

Frequently asked questions about Django

What is Django used for?

Django is a Python framework for building web applications that ships with an ORM, admin panel, user auth, migrations and protection against common attacks. It's used for larger systems like portals, internal apps and APIs, where it helps to have a lot in place from the start.

Django or FastAPI: which should I choose?

Django is the better fit for a large app with many models that needs a ready-made admin panel, while FastAPI suits fast, lightweight APIs. FastAPI validates input through Python type hints and produces interactive docs on its own, which makes it handy for smaller services.

Do you build projects in Django?

Not as my first choice. I know Django, but I don't have a portfolio project built on it, and for Python APIs in my own projects I usually choose FastAPI, with Supabase for the database and sign-in.

All skills →