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.
Pros
Scale
Performance
Encapsulation
Cost
Cons
Memory
Execution Time limits
Error Reporting
Likelihood to Recommend
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.
VU
Verified User
Engineer in Information Technology (1001-5000 employees)
[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.
Pros
This can be incredibly cheap as you use it whenever you want.
This is heavily scalable
You can Swiftly deploy and execute the code
Cons
The documentation is not very clear and could be made more informative
Plugins are very limited
Logs are very hard to debug
Likelihood to Recommend
[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.
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.
Pros
I have used the AWS Lambda for moving the RDS snapshots from cross-region like East to West and West to East. We used it as part of our DR solution. AWS Lambda is the service provided by AWS, and it makes it easy to manage the AWS resources.
I have used AWS Lambda for running a cleanup code against the database at scheduled times. I use Python as the coding language. AWS Lambda is the service provided by AWS, which makes easy to manage the AWS resources.
We can use AWS lambda function for serverless architecture.
We can use AWS Lambda for managing Micro-service architecture.
Cons
AWS Lambda has not worked in an efficient way for running long-lived applications, especially on serverless architecture.
AWS Lambda provides a zip deployment method, but there is a limit on size, like 500MB.
AWS Lambda has a significant issue with "Cold Start." It takes some time for it to handle the first request -- there, we see a real problem.
Likelihood to Recommend
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.
Pros
Easy to set up.
Support different programming languages.
Events-based trigger.
Cons
Continuous deployment integration with GitHub.
Would like to easily toggle between environments.
An interface to map out/organize different functions.
Likelihood to Recommend
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.
Pros
No need for specialist deployment engineer
It do not require any additional cost for server to debugging a code
Time-saving activity
Cons
We are not fully aware of its use but if it has functionality likewise we have in Unix like operating system where we can schedule deployment then it will be very good.
As of now, no one is trained in using any of AWS functionality fully in our team, it requires special skills to use LAMBDA.
It also requires setting up of node.js environment, which most of us found difficult.
Likelihood to Recommend
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.
