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."It is a scalable solution."
"The feature I found most valuable about Lambda is the fact that it's serverless."
"The most valuable features of AWS Lambda are a serverless and event-driven architecture."
"The ease and speed of developing the services using any available language is the most valuable feature."
"You can spin up anything instantly without any investment."
"AWS Lambda is interlinked with CloudWatch. When we have any errors we can directly go there and check the CloudWatch logs. Additionally, we can run it very fast and we can increase the RAM size and other components."
"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."
"We moved our users into the Amazon Cognito pool, so it helps us to standardize our security practices, approaches, etc. We can customize Lambda for authentication to integrate it with API Gateway and other services."
"Provides deep integration with other Azure resources."
"Real-time analytics is the most valuable feature of this solution. I can send the collected data to Power BI in real time."
"I like the IoT part. We have mostly used Azure Stream Analytics services for it"
"I like all the connected ecosystems of Microsoft, it is really good with other BI tools that are easy to connect."
"The solution's most valuable feature is its ability to create a query using SQ."
"The life cycle, report management and crash management features are great."
"The solution's technical support is good."
"It's scalable as a cloud product."
"Lambda can only be used in one account; there's no possibility to utilize it in another account."
"The running time of AWS Lambda runs fine. It takes around five minutes but it would be great if that time could be extended."
"AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job."
"AWS Lambda should support additional languages."
"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."
"AWS Lambda needs to improve its stability."
"Security needs to 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."
"The collection and analysis of historical data could be better."
"Its features for event imports and architecture could be enhanced."
"Azure Stream Analytics could improve by having clearer metrics as to the scale, more metrics around the data set size that is flowing through it, and performance tuning recommendations."
"The solution offers a free trial, however, it is too short."
"We would like to have centralized platform altogether since we have different kind of options for data ingestion. Sometimes it gets difficult to manage different platforms."
"The solution’s customer support could be improved."
"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."
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 EC2, whereas Azure Stream Analytics is most compared with Amazon Kinesis, Databricks, Amazon MSK, Apache Flink and Apache Pulsar.
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.