The scalability is a bit of an issue when you are a smaller firm because it can be quite expensive. If you are using an on-premise version, it's not as scalable because you need to buy the hardware devices. If you are using the virtual version, it's a little bit easier to scale.

There are around seven end users using this solution in our company. I would say the scalability is very high. We have over two million users and are able to handle a large volume of traffic without any problems.

IBM DataPower Gateway is a scalable product, but Hungary is a relatively small market, so even the smallest size is sometimes too big for the customer. Scaling the product downwards would be better because it's more suitable for small businesses. IBM DataPower Gateway is less applicable to mid-size and large businesses.

It is a scalable platform. I rate its scalability an eight out of ten.

I would rate the tool's scalability a ten out of ten. We have many users for the tool in our company. We have plans to increase the software's usage in the future. 

The solution is best for medium to large companies and is easy to scale. 

The solution is very scalable.

The solution is scalable, our customers are mostly South African banks and they handle mostly transactions with this solution.

It is a scalable product.

This is a supported gateway. It does not have front end users. It has a number of transactions. You compare the number of transactions, for the development and product utilization.

We have plans to continue using it in the future.

The product is scalable. In m company, six people are using the solution. I don't know if my company is planning to increase usage in the future.

We have a pretty low load. We have not had to scale it.

We have quite a few users in our organizations.

We don't have plans to increase usage in DataPower, only with IBM API Connect.

It is easy to scale as the product itself has the capability to install it as a cluster. So it can be scaled vertically or horizontally.

We have a team of about 10 developers and 10 to 15 enterprise customers globally.

The solution's scalability needs improvement.

With respect to scalability, the new IDG X2 appliances come with a lot of power inside these appliances so you won't have any issues. It comes with a 24-core machine, which should be powerful enough for your workloads.

We are using the on-premises, hardware application, so scalability comes at a cost. It means that you will need to install another application and another appliance.

It's horizontally scalable.

When using it as a certain kind of pass-thru, I've measured it to 6,000 transactions per second. If you're using it in a request-reply pattern, that comes down to about 600. The 6,000 was the limit on the testing equipment. It wasn't the limit on the product.

This solution is not scalable for our environment.

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. 

We found the scalability to be quite good. If a company needs to expand the product, it can do so.

We had about 30 developers and 1,000 end users on the solution.

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

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

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

You can scale it easily by adding on appliances as you like.

All of the people in the organization use it from administrators to end-users. All of the applications use it.

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

The solution is definitely scalable. If a company needs to grow it bigger, they are able to do so quite easily. It's designed for large-scale users (users that are 1000+). It's mostly for IT departments to use, not regular end-users.

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.