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."The ability to scale up and down very quickly helps because we can maintain our system performance and business at a low cost."
"The installation and configuration of the solution is straightforward."
"The solution offers good performance."
"We have no issues with the technical support."
"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."
"AWS Lambda is itself serverless, and it is connected to the API gateway, and you can directly call the API through the API gateway and connect through AWS Lambda."
"AWS Lambda's most valuable feature is serverless architecture."
"The initial setup is pretty easy."
"I like the IoT part. We have mostly used Azure Stream Analytics services for it"
"We find the query editor feature of this solution extremely valuable for our business."
"Provides deep integration with other Azure resources."
"We use Azure Stream Analytics for simulation and internal activities."
"The solution's most valuable feature is its ability to create a query using SQ."
"I like all the connected ecosystems of Microsoft, it is really good with other BI tools that are easy to connect."
"The life cycle, report management and crash management features are great."
"It's scalable as a cloud product."
"Its performance can be improved. There should also be more dynamic security permissions."
"We'd love to see more integration potential in the future."
"Lambda's dashboard could be more user-friendly and customizable. I want the dashboard to have more information to quickly identify what functions and events are running. Also, we want to be able to add more trigger points, push notifications, and events."
"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"
"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."
"The deployment process is a bit complex, so it could be simplified to make it easier for beginners to deploy."
"AWS Lambda has some size limitations in the code line, you can't do a couple of functions to do the job."
"I want to see support for longer applications. I need the 15-minute time-out window to improve."
"If something goes wrong, it's very hard to investigate what caused it and why."
"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."
"Sometimes when we connect Power BI, there is a delay or it throws up some errors, so we're not sure."
"The only challenge was that the streaming analytics area in Azure Stream Analytics could not meet our company's expectations, making it a component where improvements are required."
"The UI should be a little bit better from a usability perspective."
"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."
"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."
AWS Lambda is ranked 1st in Compute Service with 70 reviews while Azure Stream Analytics is ranked 4th 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 Instaclustr Managed Apache Kafka.
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.
