AWS Fargate vs Apache NiFi comparison

"We can integrate the tool with other applications easily."

"The most valuable feature has been the range of clients and the range of connectors that we could use."

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

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

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

"It is highly effective for handling real-time data by working with APIs for immediate and continuous data extraction."

"Visually, this is a good product."

"The initial setup is very easy."

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

"It allows for focusing on applications instead of managing infrastructure."

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

"AWS Fargate is a fully managed service, and it's very easy to use compared to other services like Elastic Beanstalk Service (EBS)."

"Fargate's integration with other AWS services is really good."

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

"Fargate is beneficial for hosting our solutions and providing workflow management, creating legal documents, and delivering business intelligence."

"Fargate itself is a stable product. We are quite satisfied with its performance."

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

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

"I think the UI interface needs to be more user-friendly."

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

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

"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 quality of JSON data processing could be improved, as JSON workloads require manual conversions without a specific process."

"More features must be added to the product."

"I would like to see enhanced faster application scaling and better integration with the elastic file system to unify storage volumes and improve the launch time of instances."

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

"AWS Fargate needs improvement in terms of setup complexity."

"As I have not worked with Fargate extensively, I do not have any specific improvements."

"Challenges include higher costs for smaller clients, limited control over underlying infrastructure customization, and potential latencies during task startup."

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

"There is a tool named Compose that helps in converting the Docker Compose file into a Kubernetes file. For ECS and Fargate, AWS reads a Dockerfile and helps with conversion. However, I am uncertain if it's ready for deployment after conversion."

"We faced challenges in vertically scaling our workload."

"We use the free version of Apache NiFi."

"It's an open-source solution."

"I used the tool's free version."

"The solution is open-source."

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