Hello, I would like to suggest that you include the limitations AWS Lambda
and API Gateway has, since I have used them and it is not suitable for
every use case.
For example, one of the biggest limitations is that an Lambda can run for
at most 5 minutes, but if paired with API Gateway, it can o
Yes, it calls is in a WSGI mode. I've found that response time is around
80-100ms.
On Monday, February 8, 2016 at 5:02:00 PM UTC+1, Florian Apolloner wrote:
>
> Hi Rich,
>
> to quote from your blog post:
>
>> the server is created *after* the HTTP request comes in through API
>> Gateway. It then
Hi Rich,
to quote from your blog post:
> the server is created *after* the HTTP request comes in through API
> Gateway. It then turns the API Gateway request into normal Python WSGI,
> processes the request, and returns it back through the API Gateway to the
> client.
>
Doesn't that effective
Hey guys!
(I also made this post to django-users, but I think the discussion here can
be about ways that we can improve Django to work better on AWS Lambda.
Forgive the double-post.)
I'm pleased to announce the release of Django-Zappa - a way to run
serverless Django on AWS Lambda + API Gatewa
