---
title: "Comment by For sell Mx on \"Lessons Learned from Running Serverless Applications in Production on AWS\" | Hashnode"
description: "Great summary of the core appeal. One complementary best practice is to always set conservative concurrency limits on your production Lambda functions from the"
url: "https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b/comment/69e6f085cef22a93a595d25b"
---

[Discussion](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b)

Comment [Lessons Learned from Running Serverless Applications in Production on AWS](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b)

[For sell Mx](https://hashnode.com/@mxsell)

[Apr 21](https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b/comment/69e6f085cef22a93a595d25b)

Great summary of the core appeal. One complementary best practice is to always set conservative concurrency limits on your production Lambda functions from the start. This prevents a downstream database or API outage from causing a runaway retry cycle that escalates cost and compounds the failure.