Topic 01 / 12

What is Django? The MVT Architecture Explained

~14 min read // Django Part 1 Series // Coding India

1. What is Django?

Django is a free, open-source web framework written in Python. Its guiding philosophy is captured in two phrases that appear on its homepage: “The web framework for perfectionists with deadlines” and batteries included. This means Django ships with almost everything you need out of the box — a database layer, a user authentication system, an admin panel, a templating engine, and security protections against common attacks like CSRF and SQL injection.

Django was created in 2003 by Adrian Holovaty and Simon Willison at a newspaper company. The pressures of a newsroom — ship it today, make it correct, keep it maintainable — shaped a framework that is opinionated, structured, and production-proven. Companies like Instagram, Pinterest, Disqus, and Mozilla have all run Django at scale.

2. The Model-View-Template (MVT) Architecture

Django follows a pattern called MVT — Model, View, Template. If you have heard of the MVC (Model-View-Controller) pattern from other frameworks, MVT is the Django dialect of the same idea. Here is what each layer means:

Layer	Responsibility	Analogy
Model	Defines the shape of your data and talks to the database. A `BlogPost` model, for example, describes that a post has a title, a body, and a published date.	The blueprints of a building.
View	Contains the business logic. A view receives a web request, fetches data from the Model, and decides what to send back to the browser.	The architect who reads the blueprints and decides what to build.
Template	An HTML file with special tags that Django fills in with dynamic data before sending it to the browser.	The painted walls and furniture of the finished building.

3. How Django Processes an HTTP Request

Every interaction with a Django website follows this exact sequence. Understanding this flow is the most important mental model in Django development.

Browser sends an HTTP request. A user types https://mysite.com/blog/ and hits Enter. The browser fires a GET request to your server.
The WSGI/ASGI server receives the request. A server program like Gunicorn (which we cover in Chapter 15) receives the raw HTTP bytes and hands them to Django. WSGI (Web Server Gateway Interface) is the standard protocol that defines how a Python web application talks to a web server.
Django’s URL dispatcher matches the URL. Django reads its urls.py configuration file and checks each URL pattern against the incoming path. When it finds a match for /blog/, it knows which view function to call.
The View function executes. Django calls the matched view, passing it the request object. The view queries the database (via the Model layer) and prepares a context dictionary — a bundle of data to pass to the template.
The Template is rendered. Django’s template engine takes the HTML template, fills in the dynamic variables from the context, and produces a complete HTML string.
Django returns an HTTP response. The rendered HTML is wrapped in an HTTP response object (with a 200 status code) and sent back to the browser. The browser displays the page.

Browser
  │  GET /blog/
  ▼
WSGI Server (Gunicorn)
  │
  ▼
URL Dispatcher (urls.py)
  │  path('blog/', views.blog_list)
  ▼
View Function (views.py)
  │  posts = Post.objects.all()
  ▼
Template Engine
  │  renders blog_list.html with posts data
  ▼
HTTP Response (200 OK, HTML)
  │
  ▼
Browser displays the page

4. Why Choose Django for Production?

Security by default: Django automatically protects against SQL injection, Cross-Site Scripting (XSS), Cross-Site Request Forgery (CSRF), and clickjacking. You get these protections without writing a single line of security code.
The ORM: The Object-Relational Mapper lets you define your database tables as Python classes and query the database using Python code instead of raw SQL. No SQL expertise required to get started.
The Admin Interface: With three lines of code, Django generates a full-featured, production-ready admin dashboard for managing your data.
Scalability: Django is used at Instagram scale. Its architecture allows you to add caching (Redis), background workers (Celery), and async support as your traffic grows.
Mature ecosystem: Thousands of third-party packages (Django REST Framework, Django Channels, Wagtail CMS) extend its capabilities.