Overall Satisfaction with AWS Lambda
AWS Lambda is used primarily by about 20% of our staff and only in our development department. We use AWS Lambda for developing and managing our application over the cloud platform. We internally provide cloud-related solutions to our dev groups and develop web apps and services on cloud for them. So whenever we have to provide any computation related work for that particular app than I use AWS Lambda because it is easy to use and scalable and also costs less than any previous solution we have reviewed.
- AWS Lambda is a great compute engine that allows you to run and execute your computation code without the need of maintaining servers and the overhead that comes with that.
- We all can use our favorite programming language to develop the functions.
- AWS Lambda is the fastest server setup on the market.
- The relationship with S3 Triggers leaves a lot of room for improvement.
- The solution community forums leave a lot to be desired.
- The AWS Lambda UI experience could aid an overhaul. It's not unusable but not a great reflection of how great the service product is.
- We see a positive impact on actually developer moral because they are given language freedom.
- We have also seen a positive impact in reducing the time needed to deploy Rest APIs within a project schedule. Our deployments are quicker and it helps shorten our critical paths.
- We have seen a small negative impact on monitoring and S3 triggers. They do not always seem to work so you have to pay a little closer attention then we would wish to ensure smooth operation.
We really did not evaluate them against other products except a little Google research, we are a centralized AWS customer so it was a smooth and simple (even if blind) decision for us.