What is this?
Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed. Thanks to non-blocking network I/O it can scale to tens of thousands of open connections.
Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed. Thanks to non-blocking network I/O it can scale to tens of thousands of open connections.Does it serve requests itself, or do I put it behind a separate web server?It serves traffic itself — the README titles it Tornado Web Server, and the sample app simply calls app.listen(8888). No separate web server is mentioned.
It serves traffic itself — the README titles it Tornado Web Server, and the sample app simply calls app.listen(8888). No separate web server is mentioned.How do I get a minimal app running?Subclass tornado.web.RequestHandler with a get() method, wire your handlers into a tornado.web.Application, call app.listen(8888) inside an async main(), and start it with asyncio.run(main()).
Subclass tornado.web.RequestHandler with a get() method, wire your handlers into a tornado.web.Application, call app.listen(8888) inside an async main(), and start it with asyncio.run(main()).Does it run on Python's asyncio, or does it bring its own event loop?It runs on Python's built-in asyncio: the example app listens, then waits on asyncio.Event().wait() inside main(), launched via asyncio.run(main()). No other dependencies are mentioned.
It runs on Python's built-in asyncio: the example app listens, then waits on asyncio.Event().wait() inside main(), launched via asyncio.run(main()). No other dependencies are mentioned.Do I have to write async code everywhere to use it?Not necessarily. The README notes its Hello, world example does not use any of Tornado's asynchronous features; async is introduced separately with a simple chat room example.
Not necessarily. The README notes its Hello, world example does not use any of Tornado's asynchronous features; async is introduced separately with a simple chat room example.What kind of apps is it built for?Apps where each user stays connected: the README says it is ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.
Apps where each user stays connected: the README says it is ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.Where did Tornado come from?It was originally developed at FriendFeed; the GitHub repository has existed since September 2009.
It was originally developed at FriendFeed; the GitHub repository has existed since September 2009.Is the project still alive?By its metadata, yes: the repo is not archived, has roughly 22,000 stars, and runs GitHub Actions workflows for building and testing.
By its metadata, yes: the repo is not archived, has roughly 22,000 stars, and runs GitHub Actions workflows for building and testing.What are similar projects?socket.io, ktor, aiohttp, actix-web, webserver, echo, centrifugo, starlette
socket.io, ktor, aiohttp, actix-web, webserver, echo, centrifugo, starletteWhich topics is it in?asynchronous, websockets, event-driven, web-server, scalability, web-framework, websocket, http, real-time, backend, networking, framework
asynchronous, websockets, event-driven, web-server, scalability, web-framework, websocket, http, real-time, backend, networking, framework