lambda-warmer-py VS Zappa

I've been using FastAPI in Lambda, and it's working great, but I remember having struggled with low-performing responses, and the key was to turn off the Mangum lifespan (Mangum(app, lifespan="off")). Also, instead of using provisioned concurrency, we ended up using the old-school warming method with something like this

Provisioned concurrency isn't worth it in my experience. You can just use, say, a CloudWatch rule to ping your desired number of instances every 5-odd minutes and keep them warm. 288 pings per day for 100 instances at 100ms per instance/ping is 2,880 seconds of execution time, or 5,760 GB-seconds at 2GB RAM (1 full vCPU and a bit). At $0.0000166667 per GB-second, that's $35 a year. You could cut that in half with smarter pings than e.g. [1], but it's not worth the engineering cycles at this price.

1. Python version: https://github.com/robhowley/lambda-warmer-py

Another alternative is Zappa which is built-in Python Serverless Framework and it serves only that runtime on AWS.

Also, Zappa core team is looking for contributors to manage the project. I don't know why someone would leave a project like this. It had nearly 12k stars on original repo here https://github.com/Miserlou/Zappa and has around 1.7k on the new one.

I used to work for a startup that quickly grew to become one of the biggest Lambda users in my country (according to AWS). The entire business was serverless, not just Lambda but backend DynamoDB, APIGW, Cloudfront, etc. There was maybe 2 EC2 instances in the whole company.

Having seen what that model of development can do from an operational/security/agility/scalability/efficiency perspective, I think the comments on HN about serverless saying "it's just CGI" or that they could do something similar without vendor lockin are honestly laughably ignorant. If you haven't messed with Zappa (https://github.com/Miserlou/Zappa) or Serverless Framework (https://www.serverless.com/) at least a little you are missing out.

I'm using the Zappa framework https://github.com/Miserlou/Zappa with Python and Flask on AWS Lambda. When it raises an exception it appears in the CloudWatch log but is illegible to me. I do get a normal Flask stack trace returned from a HTTP GET in debug builds however.

I have a Python 3.6 - Flask application deployed onto AWS Lambda using Zappa, in which I have an asynchronous task execution function defined using @Task as discussed here

The only similar issue I can find in my Google searches is this page, but I don't know if it's the same issue and the discussion there is going over my head.

Hi u/appliku I think Zappa has been moved from https://github.com/Miserlou/Zappa repo to its own repo and account https://github.com/zappa/Zappa Also, they released version 0.54.0 (Minor version) on Oct 14.

I like deploying on AWS Fargate or AWS Lambda using zappa for very low-cost deployments. Because Lambda has a (always) free tier usage, you can get away with hosting many sites for next-to-nothing with Zappa.

Depending on what you need zappa (https://github.com/Miserlou/Zappa) allows you to run Django in aws lambda which is very cheap (read practically free).