IBM DataPower Gateway Review

Good SQL injection features but it needs better scripting


What is our primary use case?

We use it for API Connect for gateways and we use the backend as an MQ. I implement it for our clients.

What is most valuable?

The API Connect gateway service and the SQL injection features are good. 

What needs improvement?

Scripting needs improvement. It's hard for our customers. 

For how long have I used the solution?

I have been using this solution for the last two years. 

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It is scalable. It's used daily for every backend server.

Our customers are primarily enterprise-sized. Our enterprise companies use this product. 

How are customer service and technical support?

I haven't contacted their support. 

Which solution did I use previously and why did I switch?

We did not previously use a different solution. 

How was the initial setup?

The initial setup was straightforward as it's on-premise. Cloud is trickier than on-premise. But deploying the containers is difficult. 

I did the deployment myself. It around one hour. If you want to do clustering it will take two to four hours. 

What's my experience with pricing, setup cost, and licensing?

If you want additional features, you will need to pay more. 

What other advice do I have?

It is a good solution. It's more expensive compared to competitors. IBM charges more for its products. Anybody can use it as their security device and as their multi-protocol handling device. It is compatible with IBM products. 

I would rate it a seven out of ten. 

In the next update, I would like to see better development features and more scripting options. 

Which deployment model are you using for this solution?

On-premises
**Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Add a Comment
Guest