Axway AMPLIFY Application Integration vs SAS Access comparison

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

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

"The most valuable aspect of the solution is the ease of access to the data in those databases."

"The most valuable part of SAS/ACCESS is what it is made for: connecting to remote systems that are not part of your physical SAS environment."

"The most valuable feature is you have native access to the external databases."

"Axway AMPLIFY Application Integration is an expensive solution."

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

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

"The product must improve its visibility and scalability."

"The solution can provide access to the newer databases that come out sooner."

"I can't really recall any missing feature or general improvement that is needed. We don't really add too many new kinds of databases and therefore our needs are already met."

"The pricing model needs to be reconsidered and adjusted."

"The product is not expensive."

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

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

"The pricing model is complex and is based on modular packages as well as the size of the applicable environment."

"The solution's pricing and licensing are expensive."