We performed a comparison between Apache NiFi and AWS Fargate 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. I would rate my experience with the initial setup a ten out of ten, where one point is difficult, and ten points are easy."
"It's an automated flow, where you can build a flow from source to destination, then do the transformation in between."
"The most valuable features of this solution are ease of use and implementation."
"The initial setup is very easy."
"The user interface is good and makes it easy to design very popular workflows."
"The most valuable feature has been the range of clients and the range of connectors that we could use."
"We can integrate the tool with other applications easily."
"Visually, this is a good product."
"AWS Fargate has many valuable services. It does the job with minimal trouble. It's very observable. You can see what's going on and you have logs. You have everything. You can troubleshoot it. It's affordable and it's flexible."
"The most valuable feature of Fargate is that it's self-managed. You don't have to configure your own clusters or deploy any Kubernetes clusters. This simplifies the initial deployment and scaling process."
"I like their containerization service. You can use Docker or something similar and deploy quickly without the know-how related to, for example, Kubernetes. If you use AKS or Kubernetes, then you have to have the know-how. But for Fargate, you don't need to have the know-how there. You just deploy the container or the image, and then you have the container, and you can use it as AWS takes care of the rest. This makes it easier for those getting started or if you don't have a strong DevOps team inside your organization."
"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."
"Fargate itself is a stable product. We are quite satisfied with its performance."
"If you create your deployment with a good set of rules for how to scale in, you can just set it and forget it."
"The most valuable feature of AWS Fargate is its ease of use."
"I think the UI interface needs to be more user-friendly."
"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."
"There should be a better way to integrate a development environment with local tools."
"More features must be added to the product."
"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."
"There are some claims that NiFi is cloud-native but we have tested it, and it's not."
"The use case templates could be more precise to typical business needs."
"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."
"We faced challenges in vertically scaling our workload."
"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."
"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."
"I heard from my team that it's not easy to predict the cost. That is the only issue we have with AWS Fargate, but I think that's acceptable. AWS Fargate isn't user-friendly. Anything related to Software as a Service or microservice architecture is not easy to implement. You're required to have DevOps from your side to implement the solution. AWS Fargate is just a temporary solution for us. When we grow to a certain level, we may use AKS for better control."
"If there are any options to manage containers, that would be good. That relates more to the cost point. For example, over the next three months, I'll be making a comparison between solutions like CAST AI and other software-as-a-service platforms that offer Kubernetes management with an emphasis on cost reduction."
"AWS Fargate could improve the privileged mode containers. We had some problems and they were not able to run."
"We would like to see some improvement in the process documents that are provided with this product, particularly for auto-scaling and other configuration tools that are a bit complicated."
Apache NiFi is ranked 8th in Compute Service with 10 reviews while AWS Fargate is ranked 6th in Compute Service with 7 reviews. Apache NiFi is rated 7.8, while AWS Fargate is rated 8.8. 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 Fargate writes "Efficiently auto-scales and good performance". Apache NiFi is most compared with Google Cloud Dataflow, AWS Lambda, Apache Spark, Azure Stream Analytics and Amazon EC2, whereas AWS Fargate is most compared with Amazon EC2 Auto Scaling, Amazon EC2, AWS Lambda, AWS Batch and Amazon Elastic Inference. See our AWS Fargate 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.
