IBM DataPower Gateway Reviews

I mainly use DataPower Gateway for security and integration of web services.

The most valuable feature is the security appliance, it's very secure.

The admin and user interfaces could be improved.

I've been working with this solution since 2014.

The scalability is good, though I haven't needed to scale up much. 

The initial setup isn't so easy, you need who has experience working with the solution to help.

We use a professional service to implement this solution.

DataPower Gateway is a perfect product, and I would recommend using it because it provides a lot of benefits. I'd rate this solution as nine out of ten.

DataPower is normally used as an ESB. It's mainly used to act as a mediator or act as a middleware for developing systems to send messages for ESB. We are just using DataPower as an ESB. 

I like the fact that it remains on a USB.

The performance is good. It's been very stable. 

The product is easy to integrate.

We are always looking for more features wherein it could be easily integrated with cloud applications. We are looking for either a cloud solution or a cloud integration option.

We use it from a maintenance point of view and therefore do not necessarily need extra features. 

The solution could be more user-friendly.

While it's been used in our organization for somewhere around ten years, I've personally used it here for three or four years or so. 

The solution is very stable. The company has used it for a number of years now without any issue. It's quite reliable. 

I'm not sure if the solution is scalable. I've never tried to scale the solution.

I'm not aware of any plans at this time that would include increasing usage. 

I haven't heard of any issues with technical support. They are okay. We are largely satisfied with their level of service. 

Previously, we were using the webMethods server.

I wasn't a part of the installation process. I can't speak to how easy or difficult the process was. 

We do have one or two members on the team who actually work in both DevOps and development. If needed, they can do the deployment as well. They are engineers. 

It is a licensed product. We pay for it on a yearly basis.

We'd like a solution that can integrate better with the could. However, right now we don't want to invest in that effort to evaluate certain products.

While I don't have the specific version number on hand, I know that we are using one of the latest releases. 

We hardly work with the DataPower part. It's only whenever we use it as an ESB; it supports the design features of an ESB. 

I'm pretty neutral on the product. I would not discourage or encourage others from using it. I don't use it too much myself. 

I'd rate the solution at a seven out of ten. 

We use the solution to secure APIs for our microservices.

The solution has the best authentication features that we use before integrating it with third-party products. Also, it has efficient features for troubleshooting and API security.

It is challenging to find the right resources while dealing with system errors for the solution. Thus, its support could be better. Also, its UI could be more feasible.

We have been using the solution for ten months.

The solution is stable.

We have five solution users in our organization. It has good scalability. We plan to increase its usage.

The solution's technical support team takes time to respond to the queries.

I used Apigee earlier.

I rate the solution an eight out of ten. 

We are using it for ITM API for one of our customers.

I like that it is very stable, and we never experience any downtime. 

Traceability could be improved, especially for business operations. The traceability of the transactions could be an improvement point for DataPower to work on.

It would be better if they provided JSON support. JSON protocol data has changed format. It started performing internal transformation to JSONx. This might be an additional complexity. 

I have been using IBM DataPower Gateway for more than three years. 

We do not have any stability issues around the power source. We experienced that as a physical appliance, and then we also changed it to a virtual appliance in both setups. We are very happy, especially about the stability of the product. We did not experience any downtime, even if the number of transactions increased heavily. That is the best thing.

We are not using the cloud-native version of this program. I know that IBM API connects with some other deployment patterns, but I did not experience them. The physical appliance is like a physical machine, so it is hard to scale. 

You have more flexibility with the virtual version of the appliance. For instance, compared to WSO2's API manager, and according to my experience, it is not as easy to scale physical or virtual appliances.

They have a very wide range of support globally. We are working in Turkey, and we have IBM people locally. It is easy to get support, but since the product's stability is really good, we do not need much support from the vendor.

I did not install it myself, but since it is not installed on the cloud-native environment, like OpenShift or Kubernetes, it is not a containerized version. It was harder for the third-party providers who installed the product. We have roughly six people on the maintenance and operation side of the fleet.

A third-party service provider installed this product. It requires experience, and it is not very easy for your teams to learn how to install it. You need consulting services to set up such a product in your environment.

As far as I know, they have a perpetual license for this product. They are paying perpetual fees rather than an annual subscription or annual pricing. 

I would recommend this solution to other companies, especially large enterprises. I would not recommend it to customers in the SME segment or startups or scale-ups.

On a scale from one to ten, I would give IBM DataPower Gateway an eight.