mangum VS asgiref

Hey! I was in the same place as you are, and the best solution I found was to use Mangum (https://mangum.io/). I believe it also works with Django. Mangum is an adapter that transforms lambda events into the corresponding structure to be received by your Framework API endpoints. We are currently using it with FastAPI and it's great. We code our backend without thinking about whether it will run on Lambda, and Magum takes care of the rest.

In the real world I'm never using static cloud resources. It's all serverless, containers, or horizontal auto-scaling. I let the infrastructure handle asynchronous scaling when needed. For FastAPI specifically I've used Mangum: https://mangum.io/ to provide the asynchronous invocation below the ASGI layer. Then all my FastAPI code can just be synchronous.

I discovered https://github.com/jordaneremieff/mangum which basically transforms a fastapi app to be compatible with aws lambda.

Should I create only 1 apigtw resource with 1 lambda and use mangum + fastapi for my rest api ?

Mangum: For the integration of the Aws Lambda and the Api Gateway with the FastApi

If you go the lambda route, you can use DRF (or any ASGI app) using https://mangum.io/

Yes, it's possible to wrap any asgi app to run in a lambda. Check out Mangum https://github.com/jordaneremieff/mangum

But we do not have a handler function, do we? We have a Mangum object wrapping the FastAPI application. Luckily, the Mangum object acts as a handler function, so we can just add the following in example/src/app/__init__.py:

I've used fastapi in a lambda. The package Mangum simplifies the conversion of lambda handler to a more tradition request.

uvicorn is an ASGI server that is recommended for running FastAPI applications.

I can't seem to be able to edit on mobile. OP either meant this, or its variation, such as async_to_sync and sync_to_async.

https://github.com/django/asgiref/blob/main/asgiref/sync.py

Ofc this is a python example. I have no idea how it works in different languages.

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.

Look at the intended semantics [1], and then read the implementation [2]. Can you figure out if the implementation is correct? Can you infer the possible limitations of the approach at glance? Can your async library actually handle being called with multiple event loops installed?

I have zero trust in this code and I have been bitten by fixes to this library that introduced deadlocks in my own code.

[1] https://github.com/django/asgiref#synchronous-code--threads.

[2] https://github.com/django/asgiref/blob/main/asgiref/sync.py#...

Using WebSockets in Django utilizes asynchronous Python and Django channels, making the process straightforward. Using Django channels, you can create an ASGI server, and then create a group where users can send text messages to all the other users in the group in real time. This way, you are not communicating with a particular user, but with a group, multiple users can be added.

If you're interested in the architecture itself I recommend you start by making yourself familiar with [ASGI specification](https://asgi.readthedocs.io/en/latest/) .

We switched to using strong typing derived from the asgiref for typing ASGI types, which makes Starlite the strongest type framework of its kind.