

Apache NiFi and AWS Batch compete in data management and processing. AWS Batch has a slight advantage due to its scalability and integration abilities suited for high compute demands.
Features: Apache NiFi is valued for its flexible data routing, real-time data ingestion, and visual workflow design. It supports numerous integrated endpoints, processors, and connectors, making it ideal for data flow automation without coding. AWS Batch excels in job scheduling, resource provisioning, and massive scalability. It supports containerized workloads with template-driven setup, offering flexibility and ease for compute-intensive jobs.
Room for Improvement: Apache NiFi could benefit from enhanced integration with cloud ecosystems and simplified configuration for complex tasks. Its reliance on Java may limit some real-time processing capabilities. Handling high-volume, low-latency data processes could be refined. AWS Batch can improve by reducing dependencies on AWS-specific services and offering better cost transparency. Enhancements in UI for job management and support for diverse data input types would add value. Users may seek more flexibility in real-time processing similar to other AWS services.
Ease of Deployment and Customer Service: Apache NiFi offers a versatile deployment model with notable customization but may require deeper configuration knowledge. Its integration might be complex for those unfamiliar with the infrastructure. AWS Batch integrates seamlessly with AWS services, simplifying deployment for users with AWS background. It benefits from AWS's robust customer service, catering well to users looking for managed support.
Pricing and ROI: Apache NiFi's open-source nature provides a cost-effective solution with low operational expenses, ideal for businesses with existing infrastructure aiming for strong ROI. In contrast, AWS Batch incurs higher costs due to its reliance on AWS's managed services. However, it provides significant ROI through scalable, efficient resource utilization. AWS Batch's pricing aligns with its advanced features, justifying the cost for data-intensive applications.
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.
We have noticed a 70% cost saving.
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.
Most of the issues require checking logs and configuration, so we don't need to contact the customer support team.
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.
It scales automatically based on job demand.
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.
AWS could provide better visibility into job execution and failure, as well as easier debugging and logging, which is much needed.
The pricing in Italy is considered a little bit high, but the product is worth it.
You will have to pay only for the compute time.
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.
Some features I found most valuable in AWS Batch are fully managed batch job scheduling, automatic provisioning of computer resources, integration with EC2 and Spot Instances, support for containerized workloads, and job queues and prioritization.
| Product | Mindshare (%) |
|---|---|
| Apache NiFi | 8.8% |
| AWS Batch | 9.9% |
| Other | 81.3% |

| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 1 |
| Large Enterprise | 18 |
| Company Size | Count |
|---|---|
| Small Business | 6 |
| Large Enterprise | 6 |
AWS Batch enables developers, scientists, and engineers to easily and efficiently run hundreds of thousands of batch computing jobs on AWS. AWS Batch dynamically provisions the optimal quantity and type of compute resources (e.g., CPU or memory optimized instances) based on the volume and specific resource requirements of the batch jobs submitted. With AWS Batch, there is no need to install and manage batch computing software or server clusters that you use to run your jobs, allowing you to focus on analyzing results and solving problems. AWS Batch plans, schedules, and executes your batch computing workloads across the full range of AWS compute services and features, such as Amazon EC2 and Spot Instances.
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.