Compare Tornado and TurboGears
Tornado is a Python web framework and asynchronous networking library developed at FriendFeed. 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 great for use cases that are I/O intensive (e.g., proxies) but not ideal for compute-intensive use cases.
TurboGears was born as a full stack layer on top of Pylons, and many other disparate libraries and middleware. It is now a standalone WSGI web framework designed around MVC architecture inspired by Ruby on Rails and provides all the features developes need for web development. It can also run in minimal mode and act like a microframework such as Flask.
Let's see how Tornado and TurboGears compare on various factors and features and which to choose when.
Python web framework and asynchronous networking library, which does non-blocking I/O.
A full-stack web application framework for Python.
Used by 145,000 projects.
FriendFeed, Turntable.fm, Fantamaster.it
300 job openings which list Tornado as a requirement.
3 job openings which list TurboGears in the job description.
Not as performant
as barebones or even fullstack frameworks. Extensions could impact performance adversely.
Tornado is simple and flexible.
Developers can use TurboGears as a microframework which is very flexible. However, as you start building towards a fullstack solution, it does expect things to be done in a certain way.
Ease of Learning
Tornado is not difficult to learn if the user is familiar with asynchronous and non-blocking I/O. The online resources, courses, and tutorials are not as plentiful compared to Flask or Django.
Ease of Learning
Has a learning but since it uses a lot of exisitng 3rd party libraries it becomes are little easier to onboard. It also has a decent amount of tutorials online.
Through Plugins or Extensions
No built-in support for NoSQL databases, but 3rd party libraries support asynchronous, non-blocking access. Motor
is one such library from the makers of MongoDB. However, a lot of client libraries like DynamoDB
appear to have been deprecated or not actively maintained.
Supports MongoDB out of the box using Ming ORM
. Ming ORM was developed to look like SQLAlchemy so it's easier for developers familiar with SQLAlchemy to start using it.
No built-in admin panel. No well-known 3rd party tools either.
Built-in admin panel.
No built-in support for REST API, but users can implement REST APIs manually.
Built-in security mechanisms
such as secure cookies, XSRF, DNS Rebinding and etc. Has been used in production for many years so security is generally decent.
Little built-in protection. Must be handled by developers themselves or by using 3rd party extensions.
Tornado uses custom
templating library out of the box.
Ships with internally developed Kajiki templating engine, but supports multiple templating engine including Genshi
No built-in support.
TurboGears relies on ToscaWidgets2
for building and validating forms.
Provides user authentication and also supports 3rd party authentication and authorization systems like Google, Twitter, Facebook, etc.
Ships with repoze.who which is an authentication and identity framework for WSGI applications. Read more here
Built-in support using Python's unittest
If you found this useful, please help us grow by sharing this article with your followers using the sharing icons. Every share or call out will help. Thank you.