AWS Lambda Finance and Insurance Reviews & Insights

We use a lot of Lambda for all of our customized logic needs, we no longer deploy anything on EC2. It scales and costs beautifully, but it does require a different way of not only deploying, but also thinking about your software. It's limitations are its strengths if used a appropriately.

We use a lot of Lambda for all of our customized logic needs, we no longer deploy anything on EC2. It scales and costs beautifully, but it does require a different way of not only deploying, but also thinking about your software. It's limitations are its strengths if used a appropriately.

[AWS Lambda] is being used in specific departments of the company as and when we require it because cost is involved depending upon usage. This can be integrated with multiple AWS tools like redshift, S3 and many other services that helps in easy processing of data. This has positively impacted our maintenance cost.

[AWS Lambda] is very well suited for the projects that doesn't have any infra but needs it where short running processes are required. But if your application need to run continuously than this might not be the very apt tool for you.

We use Lambda to manage workloads integrated with our API Gateway.

I think it works really well for managing workloads without the need to manage the underneath infrastructure.

AWS Lambda is an event-driven, serverless computing platform and a compute service that runs code in response to events and automatically manages the computing resources required by the code. AWS Lambda is being used by our team and across the whole organization. It's being used as part of our DR solution to run the code at scheduled times.

AWS Lambda is best for short-lived applications/codes. Configure AWS Lambda to act based on the events that are produced on certain services. It works. We used it to move the RDS snapshot from WEST to EAST and EAST to WEST whenever the RDS automatic backups are done. It helps in other scenarios, like when application teams don't have a server or don't have a place to run a job on a regular basis. Then we can leverage this AWS Lambda to run the code against the database. As I mentioned, this is not suited for long-lived applications.

AWS Lambda is mostly being used to run our hourly/daily cron jobs. It is used across the entire organization. It helped us move data between external and internal data sources to the appropriate destinations.

AWS Lambda allows us to develop certain process without setting up a server. I would recommend AWS Lambda for a process that doesn't need to be real-time or needs to be always on.

AWS Lamda is used for running code, it is used within our team only and not used within whole origination level. Since the organization, does not require to invest money in specialist software like Jenkins. Also, it reduces our team to eliminate a need for Pre-production environment as other environments can be used as Production like env's and code can be tested in other environments. In future, probably, my team may not need specialist Deploy Engineer.

Its IT future and certainly it will reduce the number of Deployment engineer posts. So, it will be gone cost-saving activity. It will be less appropriate when org system are legacy systems.