We performed a comparison between AWS Lambda and Azure Stream Analytics 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 think the most valuable feature is the agility of the solution."
"I like that it's easy to use and maintain. Lambda is good and supports different platforms, so you don't need to worry about language or maintenance."
"The solution is scalable."
"AWS Lambda's most valuable feature is serverless architecture."
"The basic feature that I like is that there is no server installation. It also has good support for various languages, such as Java, .NET, C#, and Python."
"The solution integrates well with API gateways and S3 events via its AWS ecosystem."
"We are building a Twitter-like application in the boot camp. I have used Lamda for the integration of the post-confirmation page in the application. This will help you get your one-time password via mail. You can log in with the help of a post-confirmation page. We didn’t want to setup an instance specifically for confirmation. We used the Lambda function so that it goes back to sleep after pushing up."
"The solution offers good performance."
"The most valuable features are the IoT hub and the Blob storage."
"The solution's technical support is good."
"The solution has a lot of functionality that can be pushed out to companies."
"Provides deep integration with other Azure resources."
"Technical support is pretty helpful."
"I like the IoT part. We have mostly used Azure Stream Analytics services for it"
"Real-time analytics is the most valuable feature of this solution. I can send the collected data to Power BI in real time."
"It's a product that can scale."
"The feature to attach external storage, such as an S3 or elastic storage, must be added to AWS Lambda. This is its area for improvement."
"AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job."
"AWS Lambda could improve by having no-code or low-code options because currently, you need to be able to write code well to use it."
"It would be ideal if we could use the solution across different platforms."
"My engineers work with it on a daily basis. I just don't have enough depth of knowledge about what kinds of edge cases they may have tried and found lacking. There may be some issues with some language support at one point or another because we couldn't get the underlying libraries in there. A lot of what we do is either in JavaScript, Python, or some of the non-compiled languages. I'm not sure if we've ever tried building a C# solution, for instance, in Lambda or a Java solution in Lambda. It doesn't mean those aren't its capabilities. I would rather refer to my engineers for where the boundaries are."
"AWS Lambda can improve its file system-based sharing capabilities and restrictions."
"The user-friendliness of the solution could be improved."
"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."
"Sometimes when we connect Power BI, there is a delay or it throws up some errors, so we're not sure."
"I would like to have a contact individual at Microsoft."
"One area that could use improvement is the handling of data validation. Currently, there is a review process, but sometimes the validation fails even before the job is executed. This results in wasted time as we have to rerun the job to identify the failure."
"The solution’s customer support could be improved."
"The solution could be improved by providing better graphics and including support for UI and UX testing."
"The solution's interface could be simpler to understand for non-technical people."
"There may be some issues when connecting with Microsoft Power BI because we are providing the input and output commands, and there's a chance of it being delayed while connecting."
"Early in the process, we had some issues with stability."
AWS Lambda is ranked 1st in Compute Service with 70 reviews while Azure Stream Analytics is ranked 3rd in Streaming Analytics with 22 reviews. AWS Lambda is rated 8.6, while Azure Stream Analytics is rated 8.2. The top reviewer of AWS Lambda writes "An easily scalable solution with a variety of use cases and valuable event-based triggers". On the other hand, the top reviewer of Azure Stream Analytics writes "Easy to set up and user-friendly, but could be priced better". AWS Lambda is most compared with AWS Batch, Amazon EC2 Auto Scaling, Apache NiFi, Apache Spark and Amazon Elastic Inference, whereas Azure Stream Analytics is most compared with Amazon Kinesis, Databricks, Amazon MSK, Apache Flink and IBM Streams.
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.
