3 ms·
They are good for message queue handlers. But not good for production REST API endpoints in my experience. In the context of AWS Lambda, you are talking a 29 s
by ErikAugust 6y ago
They are good for message queue handlers.
But not good for production REST API endpoints in my experience. In the context of AWS Lambda, you are talking a 29 second timeout in API Gateway. API Gateway is fairly expensive. Also, is connection pooling a solved problem?
Many times you can do better with an EC2 instance running PM2 and Express, or whatever. Like, what does Serverless Framework do locally anyway? Express? Why not just run Express?
- deleted 6y ago[deleted]
- mtnGoat 6y agoI have a production REST API endpoints backed by PHP on Lambda that are called 12k/sec on the high end. no problems since ~2017. The best part is, I never have to worry about scaling the underlying resources, if sales brings in large clients. Worst case is I ask AWS for a greater Lambda concurrency limit.