“Data API (…) allowing you to connect directly with your MySQL or PostgreSQL database”
I think Postgres is not supported by Data API, is it?
From the AWS docs: “The Data API is currently only available for Aurora MySQL and not for Aurora PostgreSQL”.
In case you’d like to learn more about the concurrency strategy to make sure a certain number of containers are warmed up, check this doc: https://github.com/dashbird/xlambda/#handling-concurrency
As a matter of fact, we can warm a Lambda. In the example you outlined, we would just warm more Lambdas than necessary. If you’re ok with the “overprovisioning” costs, it’s fine.
We don’t use requests per second (RPS), but max concurrent requests over a period of 5 minutes. Concurrent requests are much more precise for the…
I always find the “lessons learned” experiences much more valuable than “look how glorious I am” ones. Thank you very much for sharing this with us and for being honest about it. Despite what Churchill said, unfortunately, there are still people acting as:
Interested in why you inserted a Google Trends chart showing “interest over time” in the middle of a “Performance” section of the article? There isn’t even a chart title. It would give the impression to the inattentive reader that the chart compares both languages in terms of performance, wouldn’t it?
Hi Manuel, the unproductive part is about having to go through a bunch of logs that aren’t the ones I’m interested in just to get the one I need. I call it unproductive because they don’t help me to solve a particular issue.
That’s my personal experience in the real world. I have spent several minutes with this exact issue…
Hey, thanks for the article. Very useful summary to introduce people unaware of Lambda limitations. Although everything is in AWS docs, sometimes it’s difficult to really understand the impact of a limitation on real-world scenarios. You experience just solved this.