uvicorn VS starlette

There's an open discussion under the Uvicorn repository and we prepared a repository for Reproduction GitHub Repo

FastAPI is a popular Python Web framework that developers use to create RESTful APIs. It is based on Pydantic and Python-type hints that assist in the serialization, deserialization, and validation of data. In this tutorial, we will use FastAPI to create a simple "Hello World" application. We test and run the application locally. FastAPI requires a ASGI server to run the application production such as Uvicorn.

- [3] https://github.com/encode/uvicorn/issues/527

Uvicorn and Daphne are both ASGI server implementations that can be used with Django to serve your application using the ASGI protocol. Uvicorn is built on top of the uvloop library, which is a fast implementation of the event loop based on libuv, while Daphne is maintained as part of the Django Channels project and was designed to handle the unique requirements of Django applications that utilize asynchronous features, such as real-time updates, bidirectional communication, and long-lived connections.

So now we test if the application is working by running the application with uvicorn. Command has this format: uvicorn .:

Using a simple uvicorn hello world application, I was unable to replicate your case. Using the Dockerfile from your tutorial, and the example.py code from the uvicorn front page, along with your CMD, I got:

If you look at the printout after launching the app, you'll notice that Shiny is using Uvicorn under the hood. This is a common way of containerizing apps using FastAPI deployments.

You can scale with application server, by adding more processes to server requests. I use Gunicorn with Uvicorn workers.

There is also uvicorn

When writing a web app with FastAPI, using async/await and a library like uvicorn, the GIL is less of an issue as we are primarily IO bound.

Same here, but without these weird utils it doesn't get any better.

I have 7 YoE with Django. Its great at so many things. You see some code, like middlewares, and immediately understand what's going on.

Now, we also have Starlette. The base of all new, fancy asgi libraries. Here's the base middleware class.

https://github.com/encode/starlette/blob/8d7a1cacfb3e1a30cbb...

In the last couple of years I heard 'we're running fastapi on production. Wanna join us?' so many times... but the reality is that it's still not suitable for prod. Who wants to work with a code like that if you have a readable, stable Django? I'm clueless.

Correct. Yeah I’ve been trying to find stuff. It often circles back to the issue I linked (https://github.com/encode/starlette/issues/1724)

In this thread, starlette people admitting they don’t have anywhere near the tuning features necessary for more heavily sync oriented people https://github.com/encode/starlette/issues/1724

Perhaps you are thinking about Starlette, the toolkit Starlite was originally based on? But Starlette as well won't have an influence on FastAPI's Pydantic dependencies, since Starlette never dependent on Pydantic in the first place.

The framework's official website mentions a number of pros of FastAPI. In my opinion, the most useful features from a microservice perspective are: the simplicity of code (easy to use and avoid boilerplate), high operational capacity thanks to Starlette and Pydantic and compatibility with industry standards - OpenAPI and JSON Schema.

I'm under the impression if you want a python async solution starlete or starlite is a better option then fastapi due to performance and also have a lot open issues and merge requests.

Check out starlette if you haven’t yet. Those guys are a good time on their discord. I think this is the right link - I’m on mobile. https://github.com/encode/starlette

I'm primarily a back-end dev and Django/Flask used to be my goto frameworks for building websites. At my last company we deployed some FastAPI code in production, and since then I've been enjoying the Starlette framework quite a lot (which FastAPI builds on top of). And in my free time these days, I've been building a boilerplate codebase on top of Starlette so it's quicker to build user-facing applications using the framework.