

AWS Lambda and Apache NiFi compete in serverless computing and data flow management, respectively. AWS Lambda has the upper hand in scalability and ease of integration with AWS services, whereas Apache NiFi excels in data flow management with its visual interface.
Features: AWS Lambda offers scalability, easy integration with AWS services, and a serverless architecture for efficient performance. Developers appreciate its support for multiple languages and the pay-as-you-go model that eliminates the need for infrastructure maintenance. Apache NiFi focuses on visual data flow management, offering extensive processor availability and built-in provenance tracking, enabling effective data orchestration and transformation.
Room for Improvement:AWS Lambda faces challenges with cold start delays, limited non-AWS service integration, and execution time restrictions. It also requires enhancements in monitoring, debugging, and support for additional programming languages. Apache NiFi struggles with complex operations and limited cloud-native features, necessitating better integration with various data formats and improved stability and user-friendly interfaces.
Ease of Deployment and Customer Service:AWS Lambda's deployment is straightforward in public cloud environments, supported by comprehensive documentation and positive customer feedback. However, the need for paid support is sometimes viewed as restrictive. Apache NiFi, typically deployed in on-premises or hybrid environments, presents a steeper learning curve and more complex setup. While support is adequate, configuration and deployment complexities pose challenges.
Pricing and ROI: AWS Lambda provides cost-effective pay-as-you-go pricing, attractive scalability, and no upfront infrastructure costs, yielding high ROI but increasing expenses with frequent invocations. Apache NiFi, an open-source solution, offers a cost advantage for self-managed deployments. Its integration with platforms like Cloudera enhances pricing but delivers strong ROI in large-scale data processing.
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 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.
When we raise a ticket or have an issue, the support team is responsive.
Overall, it is good, but there is some room for improvement when it comes to response time and overall competence.
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 would rate how scalable AWS Lambda is a nine on a scale from 1 to 10, where 1 would be the lowest and 10 would be the highest level of scalability.
Whenever the number of requests increases, the system automatically scales up to the target we have set and scales down once the requests are resolved.
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 Lambda needs to improve cold start time.
Regarding scaling, we can add up to 1,000 execution environments for every 10 seconds per function, per region.
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.
Automatic scaling is a valuable feature. When the number of requests increases, the system automatically scales up to the target we have set and scales down once the requests are resolved.
As it is serverless, AWS Lambda has more scope for building scalable architectures.
| Product | Mindshare (%) |
|---|---|
| AWS Lambda | 14.2% |
| Apache NiFi | 8.2% |
| Other | 77.6% |

| Company Size | Count |
|---|---|
| Small Business | 5 |
| Midsize Enterprise | 1 |
| Large Enterprise | 18 |
| Company Size | Count |
|---|---|
| Small Business | 35 |
| Midsize Enterprise | 15 |
| Large Enterprise | 44 |
Apache NiFi offers a flexible platform for data orchestration, transformation, and ingestion, catering to both low and high-code customization needs. It streamlines data movement with a powerful visual interface and robust scalability, facilitating seamless integration with diverse data sources.
With Apache NiFi's drag-and-drop capabilities and extensive built-in processors, users can easily simplify complex workflows. Its open-source framework promises cost savings and increased productivity, enabling efficient pipeline development and real-time data handling. While it's valued for data integration and external tool compatibility, there's a need for improvements in logging clarity, local development integration, and cloud-native features.
What are the key features of Apache NiFi?In industries like finance, healthcare, and logistics, Apache NiFi is often implemented for data orchestration and transformation tasks, enhancing workflows through integration with tools like Spark and Elasticsearch. It supports data migration and ETL processes, enabling seamless management of large-scale data operations across systems.
AWS Lambda offers a serverless architecture that facilitates seamless integration with other AWS services, providing rapid scalability and cost efficiency. It supports event-driven computing and multiple programming languages, allowing for automatic scaling and enhanced performance.
AWS Lambda is favored for its ease of integration with AWS services like S3, API Gateway, and DynamoDB, ensuring efficient application and scaling. It supports rapid deployment with low coding requirements, parallelism, and event-triggered execution, making it suitable for event-driven processes, API services, data processing, and backend functions. While improvements in integration with external services, execution time limits, cold start latency, and support for more programming languages are needed, its price and monitoring tools could be optimized further. Users desire simplified deployments and improved documentation, especially for high-demand applications.
What are AWS Lambda's most valuable features?AWS Lambda is widely used in industries like IoT, finance, and education for its ability to handle image processing, authentication, and real-time notifications. Its flexibility and integration capabilities make it suitable for integrating CI/CD pipelines, automating workloads, and supporting event-driven processes across diverse industry applications.
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.