We performed a comparison between Apache NiFi 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 initial setup is very easy."
"The most valuable feature has been the range of clients and the range of connectors that we could use."
"The most valuable features of this solution are ease of use and implementation."
"Apache NiFi is user-friendly. Its most valuable features for handling large volumes of data include its multitude of integrated endpoints and clients and the ability to create cron jobs to run tasks at regular intervals."
"Visually, this is a good product."
"It's an automated flow, where you can build a flow from source to destination, then do the transformation in between."
"We can integrate the tool with other applications easily."
"The user interface is good and makes it easy to design very popular workflows."
"The solution offers good performance."
"Provides a good, easy path from when you're using an AWS cluster."
"The solution is highly scalable."
"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."
"Amazon takes care of the scalability. That's the right way. It's automatic and it's fully managed. That's one benefit of Lambda."
"AWS Lambda is a stable solution."
"It is a scalable solution."
"The feature I found most valuable about Lambda is the fact that it's serverless."
"There is room for improvement in integration with SSO. For example, NiFi does not have any integration with SSO. And if I want to give some kind of rollback access control across the organization. That is not possible."
"The use case templates could be more precise to typical business needs."
"There are some claims that NiFi is cloud-native but we have tested it, and it's not."
"I think the UI interface needs to be more user-friendly."
"More features must be added to the product."
"We run many jobs, and there are already large tables. When we do not control NiFi on time, all reports fail for the day. So it's pretty slow to control, and it has to be improved."
"The overall stability of this solution could be improved. In a future release, we would like to have access to more features that could be used in a parallel way. This would provide more freedom with processing."
"The tool should incorporate more tutorials for advanced use cases. It has tutorials for simple use cases."
"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 first time Lambda is started up, it takes some time to spin up an instance for serving the consumer requests. AWS has been trying to solve this in a variety of ways but have not yet managed to do so."
"If you are setting it up on hybrid solution, there is a lot of work that needs to go in."
"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."
"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."
"The price in general could always be better."
"The runtime for the solution can be improved."
"If you're running a new application with a significant load, you need to be prepared for potential bottlenecks."
Apache NiFi is ranked 8th in Compute Service with 11 reviews while AWS Lambda is ranked 1st in Compute Service with 70 reviews. Apache NiFi is rated 7.8, while AWS Lambda is rated 8.6. The top reviewer of Apache NiFi writes "Allows the creation and use of custom functions to achieve desired functionality but limitation in handling monthly transactions due to a lack of partitioning for dates". 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". Apache NiFi is most compared with Google Cloud Dataflow, Apache Spark, Azure Stream Analytics, Apache Storm and AWS Fargate, whereas AWS Lambda is most compared with AWS Batch, Amazon EC2 Auto Scaling, Apache Spark, AWS Fargate and Google Cloud Dataflow. See our AWS Lambda vs. Apache NiFi 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.
