fastapi VS Tornado

only having 1 maintainer

From the official docs:

To save time here, I have prepared a basic Python application developed on FastAPI and if you want to follow along you can get the code from GitHub Repository here.

This repository contains code for asynchronous example api using the Fast Api framework ,Uvicorn server and Postgres Database to perform crud operations on notes.

That sounds like the perfect job for our open-source lib NiceGUI. It is an UI framework on top of FastAPI. That means you can easily setup HTTPS POST endpoints to save the incoming data to a file or database. With very little effort you can also create your webpage which reads the data and displays it.

This package extends the FastAPI response model schema allowing you to have a common response wrapper via a fastapi.routing.APIRoute.

fully type-annotated options for building an API are available - one popular option is FastAPI and everything you expose is declared through pydantic. There is nothing as productive in Go I'm afraid.

For Python, I use Tornado.

I've been using Python's Tornado (http://www.tornadoweb.org/) for years now.

Now on version 6, it's fast, well maintained, mature, and has good docs with readable code.

@bdarnell has done an excellent job maintaining it.

Here's one example:

Tornado supported async style co-routines before asyncio was a thing. Now it uses asyncio under the hood by default -- and it did so with an exceptionally smooth transition.

Official Website | GitHub | PyPI

Tornado is another micro framework aimed at a specific use case: asynchronous networking applications. Tornado is well-suited for creating services that open a great many network connections and keep them alive that is, anything involving WebSockets or long polling. Moreover, It requires Python 3.5 or higher and drops Python 2 support entirely.

Yes, Mockintosh uses Tornado - a Python web framework.

Tornado