In this article, I want to share a few challenges I’ve encountered while working with a serverless stack on AWS Lambda, so you can learn from my experience.
For reference, the stack I use includes:
- Lambda
- SQS
- API Gateway
- S3
- RDS
- Several other AWS Lambda services.
Disclaimer: While I have gained expertise through my experience, I am not an expert in this field. If you have any ideas on how I can avoid these problems or if you have faced similar situations, please share! I am eager to learn and improve.
Resources handling and deployment
In a serverless stack like this, everything is a function, and all the functions are independent. While this can be great, it requires handling each function independently, for REAL. There is not just one deploy; there are many deploys, and a lot of configuration between functions (security groups, variables, dependencies, etc.).
It is important to plan ahead when dealing with a complex system, as it can quickly become a nightmare, especially if you have a medium team.
For small projects, you can manually create your functions using the AWS console. However, for larger projects, you will need a tool (or tools) to help manage them.
