StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Frameworks
  5. Django vs Tornado

Django vs Tornado

OverviewDecisionsComparisonAlternatives

Overview

Django
Django
Stacks38.7K
Followers34.8K
Votes4.2K
GitHub Stars85.6K
Forks33.2K
Tornado
Tornado
Stacks530
Followers409
Votes167
GitHub Stars22.3K
Forks5.5K

Django vs Tornado: What are the differences?

Introduction

In this article, we will explore the key differences between Django and Tornado, two popular web development frameworks.

  1. Performance: Tornado is known for its asynchronous, non-blocking I/O capabilities, making it highly performant and suitable for handling large numbers of concurrent connections. On the other hand, Django follows a synchronous approach, which may result in decreased performance when dealing with high traffic loads.

  2. Scalability: Tornado's asynchronous nature allows it to easily scale to handle thousands of connections, making it ideal for applications that require high scalability. Django, while suitable for small to medium-sized projects, may require additional configuration and setup to achieve similar scalability.

  3. Built-in Features: Django is a batteries-included framework, offering a wide range of built-in features and tools for rapid development, such as an ORM, authentication system, admin interface, and more. Tornado, on the other hand, provides a lightweight core with minimal built-in functionality, allowing developers to choose and integrate the desired components themselves.

  4. Development Approach: Django follows a conventional, monolithic approach, where a single codebase handles both the application logic and the server functionality. Tornado, however, is a microframework that focuses primarily on request handling, leaving the application logic responsibilities to the developer. This gives Tornado greater flexibility and allows for easy integration with other libraries and frameworks.

  5. Community and Documentation: Django has a large and active community, with extensive documentation and a wide range of third-party libraries and packages available. Tornado, being a relatively newer framework, has a smaller community and fewer resources available. This may result in more limited support and a smaller ecosystem of complementary tools.

  6. Learning Curve: Django follows the "batteries-included" philosophy, which can make it easier for beginners to get started and quickly build web applications. Tornado, being a more lightweight and low-level framework, has a steeper learning curve, requiring a deeper understanding of concepts such as asynchronous programming and event-driven architecture.

In summary, Django is a feature-rich framework suited for rapid development with a large community, while Tornado offers high performance and scalability with a more lightweight and flexible approach to web development.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Django, Tornado

Felipe
Felipe

May 24, 2020

Decided

Since I came from python I had two choices: #django or #flask. It felt like it was a better idea to go for #django considering I was building a blogging platform, this is kind of what #django was made for. On the other hand, #rails seems to be a fantastic framework to get things done. Although I do not regret any of my time spent on developing with #django I want to give @{#rails}|topic:null| a try some day in the future for the sake of curiosity.

438k views438k
Comments
Sandeep
Sandeep

Jun 13, 2020

Needs adviceonPythonPythonJavaScriptJavaScriptJinjaJinja

I have learned both Python and JavaScript. I also tried my hand at Django. But i found it difficult to work with Django, on frontend its Jinja format is very confusing and limited. I have not tried Node.js yet and unsure which tool to go ahead with. I want an internship as soon as possible so please answer keeping that in mind.

599k views599k
Comments
Ing. Alvaro
Ing. Alvaro

Software Systems Engineer at Ripio

May 21, 2020

Decided

Decided to change all my stack to microsoft technologies for they behave just great together. It is very easy to set up and deploy projects using visual studio and azure. Visual studio is also an amazing IDE, if not the best, when used for C#, it allows you to work in every aspect of your software.

Visual studio templates for ASP.NET MVC are the best I've found compared to django, rails, laravel, and others.

524k views524k
Comments

Detailed Comparison

Django
Django
Tornado
Tornado

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.

Statistics
GitHub Stars
85.6K
GitHub Stars
22.3K
GitHub Forks
33.2K
GitHub Forks
5.5K
Stacks
38.7K
Stacks
530
Followers
34.8K
Followers
409
Votes
4.2K
Votes
167
Pros & Cons
Pros
  • 678
    Rapid development
  • 488
    Open source
  • 426
    Great community
  • 380
    Easy to learn
  • 277
    Mvc
Cons
  • 26
    Underpowered templating
  • 22
    Autoreload restarts whole server
  • 22
    Underpowered ORM
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
Pros
  • 37
    Open source
  • 31
    So fast
  • 27
    Great for microservices architecture
  • 20
    Websockets
  • 17
    Simple
Cons
  • 2
    Event loop is complicated
Integrations
Python
Python
Python
Python

What are some alternatives to Django, Tornado?

Node.js

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Laravel

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Symfony

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Phoenix Framework

Phoenix Framework

Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase