Seamless Serverless Computing with AWS Lambda
Rating: 8 out of 10
IncentivizedUse Cases and Deployment Scope
So, in a recent task, we developed an application where user-uploaded images were getting stored in S3, triggering AWS Lambda function to resize them for uniform display. AWS Lambda also handled CRUD operations, which allows us to focus solely on business logic without managing servers. This serverless approach has streamlined development and we continue to use it for various tasks.
Pros
- Schedule Task Execution like AWS Lambda can automate tasks like cleanups and backups.
- Serverless log analysis
- Event Driven Data Processing
Cons
- AWS Lambda has a maximum execution time of 15 minutes, making it unsuitable for tasks that require longer processing times
- As AWS Lambda is Serverless, Debugging Lambda is not easy.
- cold starts in AWS Lambda can affect real time performance
Likelihood to Recommend
AWS Lambda is well suited for event driven tasks that require automatic scaling and minimal infrastructure management such as Image processing (as in our case) and Backend API's. However, AWS Lambda is less appropriate for long running processes and tasks that require consistently low latency as cold starts can introduce latency.
