We performed a comparison between AWS Compute Optimizer and AWS Lambda based on real PeerSpot user reviews.
Find out what your peers are saying about Amazon Web Services (AWS), Apache, Zadara and others in Compute Service."I find the solution's scaling capability to be an important benefit. You can scale it vertically or horizontally, i.e., you can upgrade the hardware or clone the machine. The solution is also easy to manage and flexible. Additionally, you get some layers of security without paying for it."
"We use AWS Lambda because it provides a solution for our needs without requiring us to manage our infrastructure. With the tool, we only pay for the resources we use. Additionally, it is straightforward to implement and integrates with other services like API Gateway."
"AWS Lambda's most valuable feature is serverless architecture."
"It is a scalable solution."
"Lambda being serverless is a great feature that is appropriate for our use cases."
"The installation and configuration of the solution is straightforward."
"AWS Lambda's best features are log analysis and event triggering and actioning."
"I have found all of the features valuable. It's an easy and cheap solution."
"The most valuable feature of AWS Lambda, from a conceptual point, is its functions. For example, it's mathematical templates into which you can write, and create your solution. You write small pieces of a solution under given parameters."
"I have two areas of improvement to comment on. Most of the product names in AWS are not indicative of what they are doing. Moreover, AWS is not organized and you do not have the full platform with you. It is hard to know some AWS services."
"I think that perhaps Lambda could explore its functionality more."
"We face some problems with the event-driven execution model."
"There's room for improvement in the testing setup."
"The tool changes its UI every month which is very frustrating for me. I don’t know why AWS keeps changing the UI. They can’t stick to a specific one"
"There's room for improvement in the solution's warm start, which refers to the minimum time it takes to start up a Lambda function if you haven't been running it."
"My opinion is that the integration could be improved in this solution. We have had some difficulties integrating the EC2 module, but we found a solution for that by ourselves."
"If you're running a new application with a significant load, you need to be prepared for potential bottlenecks."
"Another challenge I've noticed is that there is a limit to the environment variables such as the 4 KB limit. Although, the advice is to use parameters or other things to store the details when the limit has exceeded the data, this adds additional intensity to the application. If the size limits for environment variables can be revealed, it would be helpful. Even if we have to pay for it, at least we would know that we are not dealing with latency. So, I would like to see the size of the environment variables increased."
AWS Compute Optimizer is ranked 10th in Compute Service with 1 review while AWS Lambda is ranked 1st in Compute Service with 70 reviews. AWS Compute Optimizer is rated 8.0, while AWS Lambda is rated 8.6. The top reviewer of AWS Compute Optimizer writes "Easy to manage, flexible, and has good scaling options". On the other hand, the top reviewer of AWS Lambda writes "An easily scalable solution with a variety of use cases and valuable event-based triggers". AWS Compute Optimizer is most compared with , whereas AWS Lambda is most compared with AWS Batch, Amazon EC2 Auto Scaling, Apache NiFi, Apache Spark and AWS Fargate.
See our list of best Compute Service vendors.
We monitor all Compute Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
