Closed undiplomatic closed 5 months ago
Lambda is an ephemeral service that spins up an instance to handle each request. Async assumes that you have a long lived process that continuously handles multiple incoming requests, and implemented in order to share process power more effectively.
So async support doesn't seem to make a lot of sense when using lambda. (However, now that docker images are supported it would make sense there)
It needs investigation, but I wouldn't expect any improvement through the use of async and lambda. In fact, with the additional overhead, I would expect performance to degrade when compared to a non-async version.
(I am personally interested in FastAPI, but haven't used it since it seems to require async. BTW - I think django-ninja is similar, but not as light as FastAPI)
Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.
Hi there! Unfortunately, this Issue was automatically closed as it had not seen any activity in at least 100 days. If the Issue is still relevant to the latest version of Zappa, please open a new Issue.
Context
Django has introduced native async support. It doesn't appear to be supported by Zappa at this time. Is this something that should be supported moving forwards?
Expected Behavior
views.py
Expect output:
Actual Behavior
Possible Fix
Steps to Reproduce
Your Environment
pip freeze
:zappa_settings.json
: