

Apache NiFi and AWS Fargate compete in cloud computing, targeting different needs. AWS Fargate has an edge in scalability and infrastructure management for applications focused on flexibility, while Apache NiFi offers superior data transformation and processing capabilities.
Features: Apache NiFi offers intuitive data flow design, extensive connectors for varied data sources, and real-time analytics. AWS Fargate features serverless architecture, seamless AWS service integration, and application scaling flexibility.
Room for Improvement: Apache NiFi could enhance scalability and integration with other cloud environments, improve user-friendly interfaces for non-developers, and reduce complexity in multi-tenant setups. AWS Fargate may improve cost predictability, enhance support for non-AWS environments, and offer better application deployment transparency.
Ease of Deployment and Customer Service: AWS Fargate simplifies deployment by abstracting infrastructure, focusing on task management and offering strong AWS ecosystem support. Apache NiFi requires more hands-on deployment, needing dedicated setup resources, which might be challenging for some projects.
Pricing and ROI: Apache NiFi's costs fluctuate based on infrastructure with ROI linked to data processing tasks. AWS Fargate's serverless pricing charges by resource usage, potentially offering higher ROI for applications with variable demands.
Thanks to improvements on both our side in how we run processes and enhancements to Apache NiFi, we have reduced the time commitment to almost not needing to interact with Apache NiFi except for minor queue-clearance tasks, allowing it to run smoothly.
It supports not just ETL but also ELT, allowing us to save significant time.
There may be return on investment based on the technology and easily moving our workloads onto Apache NiFi from our previous system.
The pay-as-you-go pricing model of AWS Fargate was one of the major drivers for us to move there because we reduced costs while increasing the quality of the processing services by about 30%.
The customer support is really good, and they are helpful whenever concerns are posted, responding immediately.
Customer support for Apache NiFi has been excellent, with minimal response times whenever we raise cases that cannot be directly addressed by logs.
I would rate the customer support of Apache NiFi a 10 on a scale of 1 to 10.
Even though we didn't contract support, every two weeks I had a 30-minute meeting with a cloud architect from AWS to help our team use different products of AWS, especially with SageMaker for a forecasting algorithm we were developing.
For pro support, AWS charges additional fees.
Depending on the workload we process, it remains stable since at the end of the day, it is just used as an orchestration tool that triggers the job while the heavy lifting is done on Spark servers.
Scaling up is fairly straightforward, provided you manage configurations effectively.
Based on the workload, more nodes can be added to make a bigger cluster, which enhances the cluster whenever needed.
I have seen Apache NiFi crashing at times, which is one of the issues we have faced in production.
Apache NiFi is stable in most cases.
Apache NiFi should have APIs or connectors that can connect seamlessly to other external entities, whether in the cloud or on-premises, creating a plug-and-play mechanism.
The history of processed files should be more readable so that not only the centralized teams managing Apache NiFi but also application folks who are new to the platform can read how a specific document is traversing through Apache NiFi.
The initial error did not indicate it was related to memory or size limitations but appeared as a parsing error or something similar.
For a company that does not require complexity or managing Kubernetes clusters, AWS Fargate is a great way to go.
AWS Fargate is pretty straightforward for simple tasks and it should remain this way; an additional feature would make it complex and possibly not so stable.
They need to improve some UI-based interaction.
The pricing in Italy is considered a little bit high, but the product is worth it.
Apache NiFi has positively impacted my organization by definitely bridging the gap between the on-premises and cloud interaction until we find a solution to open the firewall for cloud components to directly interact with on-premises services.
Development has improved with a reduction in time spent being the main benefit; before we needed a matter of days to create the ingestion flows, but now it only takes a couple of hours to configure.
The ease of use in Apache NiFi has helped my team because anyone can learn how to use it in a short amount of time, so we were able to get a lot of work done.
It's very fast in terms of scaling my containers; it's much faster than other solutions.
One of the best features of AWS Fargate is that it was useful for us because we didn't require to run container workloads and we didn't need to deal with the management of a Kubernetes cluster directly, and the ability to run those workloads just in a scheduled manner is also a great feature.
What I find best about AWS Fargate is that compared to deploying containers on EC2, where we need to check everything manually such as uptime, error logs, and other issues, AWS Fargate manages all these aspects automatically.
| Product | Market Share (%) |
|---|---|
| AWS Fargate | 9.8% |
| Apache NiFi | 9.5% |
| Other | 80.7% |
| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 1 |
| Large Enterprise | 18 |
| Company Size | Count |
|---|---|
| Small Business | 10 |
| Midsize Enterprise | 4 |
| Large Enterprise | 7 |
A new compute engine that enables you to use containers as a fundamental compute primitive without having to manage the underlying instances. With Fargate, you don’t need to provision, configure, or scale virtual machines in your clusters to run containers. Fargate can be used with Amazon ECS today, with plans to support Amazon Elastic Container Service for Kubernetes (Amazon EKS) in the future.
Fargate has flexible configuration options so you can closely match your application needs and granular, per-second billing.
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.