Item: AWS Lambda
Rating: 6
Author: Fabricio Zubelli

Overall Satisfaction with AWS Lambda

Use Cases and Deployment Scope

We utiliza AWS Lambda to execute jobs and connects async executions to the rest of AWS services. AWS Lambda is also used based on events triggered by other AWS services or our application. In a particular case example you can use Lambda to send a email to a customer after some event happens and your application call the Lambda run.

Pros and Cons

Pros

Asynchronous jobs
Recurring jobs
Scoped code execution
Event follow up

Cons

Interface
Usage
Debugging

Return on Investment

Lower cost to run jobs, approximately 70%+
Quick wins on events follow up, reducing time to execute idea to action by 80%
Easy integration with AWS, reducing implementation time by 90%

Usability

It has a lot of capabilities and integrations, but debugging, logging and usage is not as straightforward as it could be.

Alternatives Considered

Cloudflare Workers

We chose AWS because of its native integrations with other AWS products.

Key Insights

Do you think AWS Lambda delivers good value for the price?

Yes

Are you happy with AWS Lambda's feature set?

Yes

Did AWS Lambda live up to sales and marketing promises?

Yes

Did implementation of AWS Lambda go as expected?

Yes

Would you buy AWS Lambda again?

Yes

Other Software Used

Amazon RDS Performance Insights, PostgreSQL, Amazon Simple Notification Service (SNS)

Likelihood to Recommend

Well suited for asynchronous specific job execution, such as a follow up process after some event
Not suites for long running multi purpose job such as running a whole application or jobs that requires storing and passing info in memory

AWS Lambda Feature Ratings

Comments

Please log in to join the conversation

Easy to integrate servers less functions