r/serverless • u/mathankumart • Jun 02 '26
We put Lambda in our latency-sensitive API path. Here's what we learned
https://blog.mathankumar.in/my-experiments-with-backend-systems-aws-lambda-beyond-the-happy-path-ce26dbbbdf0dWe started using Lambda the right way — async, event-driven, retry-friendly workloads. Then it slowly crept into latency-sensitive API paths. That's when things got messy.
What we ran into:
- Cold starts hitting user-facing requests on low-QPS and spiky-traffic APIs
- One-invocation-per-environment model quietly exhausting downstream connection pools at scale
- Provisioned concurrency helping, but shifting us back into capacity planning territory
- VPC attachment adding more operational complexity than we'd accounted for
- Observability gaps — healthy invocation rate ≠ healthy service
The fix wasn't "stop using Lambda." It was getting honest about which workloads need elasticity vs. which need predictability. Those are different requirements, and the same execution model doesn't serve both.
Duplicates
aws • u/mathankumart • Jun 02 '26