We performed a comparison between Amazon EC2 and AWS Lambda based on real PeerSpot user reviews.
Find out in this report how the two Compute Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature is autoscaling."
"The most valuable feature of this solution is the ability to have standard operating systems along with the Windows, Linux operating systems, and their maintenance-free structure, which we prefer."
"The most valuable feature is EC2 is scalable, so when you want to move to market, you don't need to wait until your provision is fast, you can just go and provision it and then easily install your application."
"The initial setup is straightforward."
"The most valuable features are the scalability options, low maintenance, and options to upgrade. AWS support is also pretty good. The generation upgrade is pretty simple and standardized."
"EC2 provides a lot of flexibility. If you don't want to have a separate on-premise database, you can put it on the cloud with EC2. You can adjust the instance type according to your needs. You select a size and get a certain amount of specific memory, CPUs, etc. You set the redirect limit, and from there, you install the software, database servers, application servers, and whatever you want."
"I use it for NextCloud and for developer purposes."
"This is a user-friendly solution."
"The solution runs on the latest cloud technology so it is easy to deploy cloud-native projects."
"The tool scales automatically based on the number of incoming requests."
"AWS Lambda's most valuable feature is serverless architecture."
"The cool thing about AWS Lambda is that AWS does all the management. For compression, it is all about making the data small and then making it regular size again. We have an encode function and a decode function. AWS Lambda schedules each of those for us. It has a load balancer and all the fancy stuff, depending on the demand. The most valuable part of AWS Lambda is that I only need to write the software. I need to write two functions, and my cloud developer turns them into two AWS Lambda instances. That's it."
"The ease and speed of developing the services using any available language is the most valuable feature."
"The stability is good."
"The initial setup of AWS Lambda is very straightforward and quick."
"It's also suitable for companies of any size. For example, we're a large enterprise, and we've used Lambda without any problems in the last 10 months."
"If the solution was cheaper, if the price was less, it would be better."
"Amazon EC2 could improve by having integration with other cloud systems, such as Azure, and Google Cloud which would be good. Additionally, having integration with on-premise systems would be appreciated."
"EC2 is a little expensive."
"I would like to see as much automation for data validation as possible in the future."
"Its price can be reduced."
"The GUI used to deploy EC2 must be improved."
"The ease of migrating applications could be improved."
"am concerned about the tool's data security."
"What could be improved in AWS Lambda is a tricky question because I base the area for improvement on a specific matrix, for example, latency, so I'm still determining if I can be the judge on that. However, room for improvement could be when you're using AWS Lambda as a backend, it can be challenging to use it for monitoring. Monitoring is critical in development, and I don't have much expertise in the area, but you can use other services such as Xray. I found that monitoring on AWS Lambda is a challenge. The tool needs better monitoring. Another area for improvement in AWS Lambda is the cold start, where it takes some time to invoke a function the first time, but after that, invoking it becomes swift. Still, there's room for improvement in that AWS Lambda process. In the next release of AWS Lambda, I'd like AWS to improve monitoring so that I can monitor codes better."
"I have seen some drawbacks with certain integrations."
"Lambda could be improved in the sense that some of the things done with Lambda function take some time. So the performance could be better and faster."
"The solution should continue to streamline integrations with AWS services."
"Its price should be improved. Its pricing is on the higher side. I am not sure if it currently supports the Go language. If it doesn't support the Go language, they can introduce it."
"The deployment process is a bit complex, so it could be simplified to make it easier for beginners to deploy."
"We need to better understand Lambda for different scenarios. We need some joint effort between Amazon and the users to have the users identify how they can really leverage Lambda. It's not about Lambda itself; it's about the practice, the guidance. There needs to be very good documentation. From the user perspective, what exists now is not always enough."
"There's room for improvement in the testing setup."
Amazon EC2 is ranked 4th in Compute Service with 56 reviews while AWS Lambda is ranked 1st in Compute Service with 70 reviews. Amazon EC2 is rated 8.6, while AWS Lambda is rated 8.6. The top reviewer of Amazon EC2 writes "Easy to scale and valuable features include the security group and key management". 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". Amazon EC2 is most compared with AWS Fargate, Apache Spark, Apache NiFi, AWS Batch and Google App Engine, whereas AWS Lambda is most compared with AWS Batch, Amazon EC2 Auto Scaling, Apache NiFi, Apache Spark and Azure Stream Analytics. See our AWS Lambda vs. Amazon EC2 report.
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.
