Axway AMPLIFY Application Integration vs Azure Data Factory comparison

"Axway AMPLIFY Application Integration is quite a stable solution."

"Axway AMPLIFY Application Integration is very easy to use."

"The most valuable feature is that API Gateway is extremely flexible for any feature, such as connecting to Active Directory to pull the users and their authentication information. There are three ways to connect to Active Directory, and the reason for this is that the computing environments of our customers are very different. Every feature in API Gateway has got multiple methodologies for accomplishing those tasks, which is important because customers are constantly changing their security models, IT models, networks, etc. API Gateway is very flexible. It is not a one size fits all sort of situation where it is very rigid, and you can only use these pull-down menus, and that's all it ever does. It is much more open than that. It can give you fabulous reports on your users, usage, security issues, and the data sets that are going through there. You'll suddenly have visibility on the movement of data within or between your organization and other organizations. The other thing is that you're connecting API to API, which is machine to machine. The things that were done manually in an Excel spreadsheet before exchanging data through email are now done machine to machine and server to server. It speeds up the velocity of your business."

"The product is robust."

"ADF is another ETL tool similar to Informatica that can transform data or copy it from on-prem to the cloud or vice versa. Once we have the data, we can apply various transformations to it and schedule our pipeline according to our business needs. ADF integrates with Databricks. We can call our Databricks notebooks and schedule them via ADF."

"It is easy to integrate."

"The data copy template is a valuable feature."

"I like that it's a monolithic data platform. This is why we propose these solutions."

"The user interface is very good. It makes me feel very comfortable when I am using the tool."

"The flexibility that Azure Data Factory offers is great."

"The most important feature is that it can help you do the multi-threading concepts."

"The solution can scale very easily."

"Because it is so flexible, you really need someone who knows Axway Gateway or has been through the training and is certified. Just because you know APIs doesn't mean you're going to walk into that API Gateway and understand what to click on. If you're going to get something done quickly, you need to find an engineer from a company who has some experience with it. It is easy to learn, but if you're doing on-the-job training, it is going to take you longer to get your project accomplished."

"Axway AMPLIFY Application Integration is an expensive solution."

"The most important point to improve is the capability to deploy in large enterprises."

"The product must improve its visibility and scalability."

"There is always room to improve. There should be good examples of use that, of course, customers aren't always willing to share. It is Catch-22. It would help the user base if everybody had really good examples of deployments that worked, but when you ask people to put out their good deployments, which also includes me, you usually got, "No, I'm not going to do that." They don't have enough good examples. Microsoft probably just needs to pay one of their partners to build 20 or 30 examples of functional Data Factories and then share them as a user base."

"Areas for improvement in Azure Data Factory include connectivity and integration. When you use integration runtime, whenever there's a failure, the backup process in Azure Data Factory takes time, so this is another area for improvement."

"Azure Data Factory uses many resources and has issues with parallel workflows."

"The product's technical support has certain shortcomings, making it an area where improvements are required."

"They require more detailed error reporting, data normalization tools, easier connectivity to other services, more data services, and greater compatibility with other commonly used schemas."

"In the next release, it's important that some sort of scheduler for running tasks is added."

"Lacks a decent UI that would give us a view of the kinds of requests that come in."

"The performance could be better. It would be better if Azure Data Factory could handle a higher load. I have heard that it can get overloaded, and it can't handle it."

"The product is not expensive."

"Users need to pay an annual licensing fee for the solution."

"API Gateway is priced on the number of transactions you run through it. API Gateway is free, and you can install as many API Gateways as you like or are necessary for your network. For example, if all of the data is inside your network or firewall, you may just need one API Gateway. If you have external customers trying to come into your organization through your firewall, you're going to need one API Gateway outside the firewall and one inside the firewall. If you have a lot of remote offices, you may want to put API Gateway in some of those offices as well. They only charge you for your usage of it. In other words, the number of transactions going through it. That's a good benefit."

"Our licensing fees are approximately 15,000 ($150 USD) per month."

"The solution's fees are based on a pay-per-minute use plus the amount of data required to process."

"It's not particularly expensive."

"Pricing is comparable, it's somewhere in the middle."

"The pricing is a bit on the higher end."

"There's no licensing for Azure Data Factory, they have a consumption payment model. How often you are running the service and how long that service takes to run. The price can be approximately $500 to $1,000 per month but depends on the scaling."

"Product is priced at the market standard."

"I rate the product price as six on a scale of one to ten, where one is low price and ten is high price."