AWS Fargate vs Apache NiFi comparison

"Visually, this is a good product."

"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."

"The initial setup is very easy."

"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."

"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."

"The most valuable features of this solution are ease of use and implementation."

"The user interface is good and makes it easy to design very popular workflows."

"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."

"We appreciate the simple use of containers within this solution, it makes managing the containers quick and easy."

"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."

"If you create your deployment with a good set of rules for how to scale in, you can just set it and forget it."

"By using a server's compute resources, one can observe the resource metrics. With AWS, one can determine when servers will be used based on CloudWatch results. For example, CloudWatch informs the application and service platform when the hit ratio has reached the threshold value."

"AWS Fargate is an easy-to-use tool to simplify setup. You only pay for the resources you use. If you need to quickly create, delete, or scale applications without managing resources like EC2 instances, Fargate is the best service to use."

"The most valuable feature of AWS Fargate is its ease of use."

"There are some claims that NiFi is cloud-native but we have tested it, and it's not."

"More features must be added to the product."

"The use case templates could be more precise to typical business needs."

"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 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 tool should incorporate more tutorials for advanced use cases. It has tutorials for simple use cases."

"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."

"There should be a better way to integrate a development environment with local tools."

"Service computing is not as straightforward compared to other computing services. It requires more effort to use effectively."

"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."

"The main area for improvement is the cost, which could be lowered to be more competitive with other major cloud providers."

"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."

"We faced challenges in vertically scaling our workload."

"AWS Fargate could improve the privileged mode containers. We had some problems and they were not able to run."

"I would like to see the older dashboard instead of the newer version. I don't like the new dashboard."

"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."

"It's an open-source solution."

"I used the tool's free version."

"The solution is open-source."

"We use the free version of Apache NiFi."

"We would advise that this solution has a slightly-higher price point than others on the market. There is a free plan available for start-ups, but the free and lower range licensing models do not provide the full functionality."

"I rate the price of AWS Fargate a four out of five."