With a highly variable load, our idle cost is pretty much zero, and we haven't had any scale barriers, so we've scaled smoothly.

With AWS Lambda, we found it easy to integrate with other AWS services such as S3, SQS, RDS, etc. This allows us to scale our services in an almost unlimited fashion, as data input into S3 sometimes peak up to a thousand objects and need to be processed as soon as possible.

Lambda is the preferred compute option because of on-demand cost. We don't have to provision any hardware beforehand. We don't have to provision the capacity required for the services because it is serverless. 

AWS takes care of things behind the scenes and we pay only for usage. We don't have to incur uptime or the upfront cost to procure a EC2 instance or create any ECS service.

AWS Lambda has helped my organization by making it easier to code and it is less costly.

AWS Lambda improved our productivity and also enabled the business teams to build their ingestion systems at ease.

All of the features are very good and useful.

Lambda has improved our organization by making it possible to transform data.

The solution has helped our organization with cost optimization. So we have used AWS Lambda for consolidated billing.

Because Lambda is serverless, it has optimized our resources. There's no need to worry about capacity. 

The solution has improved our organization by providing us with better communication with the different services, dependencies, and implementations our clients require. The solution is faster and the consumption is really good.

There are some restrictions. For example, we have some services that if you have more than 60 seconds in consumption of this service, we don't use it, because they have that restriction with the gateway. Those services we implement with Fargate and with Docker.

AWS Lambda has improved my company through its usage in a distributed system, particularly event-driven architecture. When an event is passed to AWS Lambda from Amazon SQS asynchronously, the tool can call an ETL job, and it can trigger that job, and that job can trigger an AWS Lambda function, which can then send a message to the queue to complete the entire use case.

Easy to impliment without any environment provisioning

We moved our users into the Amazon Cognito pool, so it helps us to standardize our security practices, approaches, etc. We can customize Lambda for authentication to integrate it with API Gateway and other services.

This solution has improved our ability to scale as per demand and to focus on core business functions rather than the platform.

It has made things a lot easier in terms of restoring if we need to and just not having to worry about the small things.

My automation test story is we moved from CircleCI to Jenkins, then to AWS. The benefit I can see is the maintenance and budget. Ops made this decision but it did not affect automation tests and the release pipeline too much, but I have seen the release pipeline has been developing much faster.