Overall Satisfaction with AWS Lambda
We use AWS Lambda to upload data from API to store in AWS. We have also integrated it with AWS DynamoDB, Redshift, S3, Kinesis, MSK, and many other AWS Services for further processing of the stored data. It is being used by a single department. It reduces the maintenance cost and makes development easy. Makes it easy to address any issues in the APIs without any problem to the other Lambda.
- Serverless Framework. Easy to develop and test in local environment
- Easy to detect issues. As it does not interlink to any other lambda.
- There are shared layers in Lambda that can provide common code to be shared between Lambda. Helps in Avoiding the same code to be written multiple times.
- Difficult to identify all permission issues at once. It would be easier if we can get a list of all permissions which are required to further proceed.
- Lambda output to trigger more Services. Currently, it supports only 2-3 Services.
- It would be great if AWS can handle the Lambda cold starts internally.
- Fast development
- Perfect sprint planning because of very less overhead and more room for development.
- Quick integration with other AWS Services.
- AWS CloudFormation, AWS CodeBuild, AWS CodeCommit, AWS CodeDeploy, AWS CodePipeline, AWS Identity & Access Management, AWS Lambda, AWS Key Management Service, AWS Secrets Manager, AWS Systems Manager, Amazon S3 (Simple Storage Service), Amazon EMR (Elastic MapReduce), Amazon DynamoDB, Amazon CloudWatch, Amazon CloudFront, Amazon API Gateway, Amazon ElastiCache, Amazon Elastic Compute Cloud (EC2), Amazon Kinesis, Amazon Managed Streaming for Apache Kafka (Amazon MSK), Apache Kafka, Amazon Redshift, Amazon Relational Database Service (RDS), Amazon Route 53, Amazon Simple Notification Service (SNS), Amazon Simple Queue Service (SQS), Amazon Virtual Private Cloud (VPC) and Amazon Web Services
When we use Lambda, we do not need to worry about the infrastructure and costs. AWS can handle it all on its own. For an optimum use case, one can always use AWS Lambda along with API Gateway and Route 53 for the best use case. Cloudwatch can help you identify any issues and help in monitoring the Lambda's. Lambda is cheap and best and has all you need if you are doing simple processing. If you need to do any heavy data processing, then EMR is preferred.
Do you think AWS Lambda delivers good value for the price?
Are you happy with AWS Lambda's feature set?
Did AWS Lambda live up to sales and marketing promises?
Did implementation of AWS Lambda go as expected?
Would you buy AWS Lambda again?
AWS Lambda is most suited as a Serverless methodology. When you do not want to handle the software and only want to work on logic and code development, AWS Lambda is the best option. You can also trigger AWS Lambda from many AWS services like when a new row is added into DynamoDB or when a new file is uploaded to S3 or also when you want to execute Lambda once a day or at a specific intervals(cron jobs).