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. AIOHTTP vs Tornado

AIOHTTP vs Tornado

OverviewComparisonAlternatives

Overview

Tornado
Tornado
Stacks530
Followers409
Votes167
GitHub Stars22.3K
Forks5.5K
AIOHTTP
AIOHTTP
Stacks125
Followers143
Votes0
GitHub Stars16.1K
Forks2.2K

AIOHTTP vs Tornado: What are the differences?

Introduction

In this article, we will discuss the key differences between AIOHTTP and Tornado, which are both popular Python web frameworks. By understanding these differences, developers can choose the framework that best suits their needs and requirements.

  1. Concurrency Model: AIOHTTP is built on top of asyncio, which is a library for asynchronous programming in Python. It utilizes coroutines and event loops to achieve high concurrency, allowing multiple tasks to be executed concurrently. On the other hand, Tornado follows a traditional "single-threaded with event loop" model, where it uses non-blocking I/O to handle multiple connections simultaneously.

  2. Performance: Due to its asynchronous nature, AIOHTTP can handle a large number of concurrent connections efficiently. It is well-suited for applications that require high performance and scalability. Tornado also offers good performance but is more suitable for applications that require long-lived connections or streaming data.

  3. Ease of Use: AIOHTTP provides a simple and intuitive API for building web applications. It supports both server-side and client-side programming, making it versatile for various use cases. Tornado, on the other hand, has a more complex API and requires a thorough understanding of its asynchronous nature. It may have a steeper learning curve for developers who are new to asynchronous programming.

  4. Middleware and Plugins: AIOHTTP has a middleware system that allows developers to add custom logic to the request/response processing pipeline. It also has a variety of plugins available for easy integration with third-party services. Tornado, on the other hand, follows a different approach by using Mixins and Decorators to add functionality to request handlers.

  5. Community and Ecosystem: AIOHTTP has gained popularity in recent years and has a growing community of developers. It has an active ecosystem with numerous libraries and tools available for various use cases. Tornado, on the other hand, has been around for a longer time and has a mature ecosystem with a wide range of community-contributed modules and libraries.

  6. Compatibility: AIOHTTP is a pure Python library and can run on various platforms and Python versions. It supports Python 3.6 and above. Tornado, on the other hand, also supports Python 3.x versions but has limited compatibility with Python 2.x.

In summary, AIOHTTP and Tornado are both powerful web frameworks with different approaches to handling concurrency and asynchronous programming. AIOHTTP is well-suited for applications that require high performance and scalability, while Tornado is more suitable for long-lived connections and streaming data. Developers should consider their specific requirements and skillset when choosing between these frameworks.

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

Detailed Comparison

Tornado
Tornado
AIOHTTP
AIOHTTP

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.

It is an Async http client/server framework. It supports both client and server Web-Sockets out-of-the-box and avoids Callback. It provides Web-server with middlewares and pluggable routing.

-
asyncio; client; server;
Statistics
GitHub Stars
22.3K
GitHub Stars
16.1K
GitHub Forks
5.5K
GitHub Forks
2.2K
Stacks
530
Stacks
125
Followers
409
Followers
143
Votes
167
Votes
0
Pros & Cons
Pros
  • 37
    Open source
  • 31
    So fast
  • 27
    Great for microservices architecture
  • 20
    Websockets
  • 17
    Simple
Cons
  • 2
    Event loop is complicated
No community feedback yet
Integrations
Python
Python
No integrations available

What are some alternatives to Tornado, AIOHTTP?

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.

Django

Django

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

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.

ExpressJS

ExpressJS

Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.

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.

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