---
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 explicit concurrency limits on your production Lambda functions. This prevent"
url: "https://hashnode.com/posts/lessons-learned-from-running-serverless-applications-in-production-on-aws/67fe329f647f06e151034e8b/comment/69cb84f6b8182ec0fb217d72"
---

[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)

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

Great summary of the core appeal. One complementary best practice is to always set explicit concurrency limits on your production Lambda functions. This prevents a traffic surge from overwhelming downstream resources like your DynamoDB table, adding a crucial safety net to that automatic scaling.