It is a scalable product.

This is a scalable solution. 

I would rate the scalability of Apigee as a seven out of ten.

It's a scalable product. I don't have a problem with scaling since I contract with the service, and I don't have to worry about how they scale.

There are five of us that working on the solution currently. They are primarily architects that help with the development.

I'm quite confident of the scalability. I did do some comparisons between MuleSoft and Apigee, and a third one whose name slips my mind at the moment.

With Apigee, we don't have to think about scaling. There are still some limits, however, you can buy up. They have 80 million transactions a year, 80 million or 800 million, however, you can buy up if you start to exceed that. On some of the other platforms, you have to post the service yourself and you have to make sure that you were managing scale. That was one thing that is an advantage on Apigee.

There are something like 60,000 users using the solution, however, our load plan around it is more so that I don't think we've fully deployed it to the extent that we plan to. It's probably a small effect of that. The number of users that are impacted by it is probably in the order of nearly 10,000.

It's not being used as much as we would like. We're still ramping up and prioritizing people to be building around. Some of our existing technology does not traverse through it. Over time, we do plan to extend it until all of our external-facing interfaces go through Apigee.

The system is scalable; however, achieving scalability involves updating numerous properties and parameters. While it is manageable, the learning curve proved significant, and we gained insights through collaboration with a team of three during the development process.

The scalability is good. Our load has improved drastically in the last three years. The traffic has been increased, and we still see a good performance overall.

Mostly developers from different teams use it. And there are administrative teams maintaining the overall solution within the organization.

Apigee is a pretty scalable solution. Approximately ten developers use Apigee in our organization. The traffic that we have is close to 10,000 API requests a day.

I rate Apigee a nine or ten out of ten for scalability.

We have 20 to 30 people using the solution. 

I rate the tool’s scalability an eight or nine out of ten.

It is a scalable solution.

Apigee is scalable. It can handle a decent amount of traffic.

We have 15 architects and developers using this solution in my organization.

The scalability of the solution is okay. If a company needs to scale it, it should be able to do so.

Currently, we only have about ten people on our team that use it.

Apigee is scalable.

I think it's pretty scalable. Currently, we are doing about sixteen million calls per quarter. As we are not using it on a large scale, we don't usually have latency issues whatsoever. We have a clustered environment and there is little to no downtime, even when we are running patches on the operating system. We have between twenty-five and thirty regular developers that use this platform. We have four nodes in the cluster that are serving internal traffic, and then we have another four nodes for external traffic so that way we don't really require any upgrade.

At this time there is no immediate need to scale up the environment. We have four servers with four nodes in the cluster that service the internal traffic, and we have another four gateway nodes for the external traffic.

On a scale of one to ten, I would rate the scalability around an eight. We currently have around twenty users implementing the solution on a regular basis.

Right now, in the development area of Apigee, we have about 20 developers, architects, et cetera. We are in the process of training because our expected growth drives us to have about 100 developers by the end of next year. I think that by the end of Q1, next year, we're going to double our capacity. By mid-year, we have to have 20 more, and so on, until the end of the year. We are planning to have about 100 trained developers, or configuration experts, in Apigee.

Apigee is a scalable solution.

The solution is scalable and it's great for enterprise companies.

It's scalable. You can onboard multiple partners.

The scalability depends on your configuration. You can make it scalable.

Other vendors are basically giving more. For example, Azure. Azure is cloud-based, so they offer many things, including client support and hosting. So if you take Azure for all your storage and hosting, then they are inclined to use their API data solution. Similarly, MuleSoft provides you many things. It is an ESB kind of service broker, so you can connect to many varieties of backends. It supports that, so they can use Mulesoft API. Apigee provides a number of out-of-the-box policies and it handles the API governance. But if are looking for an end-to-end solution, Apigee is a bit behind. But if it is combined together with Google Cloud, and if the Google cloud offerings are comparable to Azure, then probably Apigee will lead.

I have around 500-2000 users using the solution in my company. It serves the purpose of my use case.

The solution is scalable, and multiple users utilize it in our organization.

Scalability wise, I've heard from some customers that Apigee has some limitations on scalability, but we haven't experienced those as of yet.

As far as Layer 7 is concerned, it seems that the policies are very deterministic as to how the actual gateways function. Some of them have had a significant impact and we've had to scale up their clusters just to support a minimal load. Some are disappointed with the number of services that we have to engage for Layer 7, and the number of clusters we've had to create. We've had to create a pretty large cluster for supporting some applications.

The Layer 7 gateway's front end is for a high-end brand product. We have the largest loyalty program in Canada. Our PC Optimum program, for instance, uses our Layer 7 gateways. There are 14 million users that use the PC Optimum card that goes through those gateways.

The solution is scalable.

We have three banking clients on the solution. 

The amount of users depends on the customer. Some use it internally. Others expose the API to clients. Some have more than a billion APIs. Some have less. 

Apigee is a cloud solution, and it's scalable. I have about two departments using it predominantly to share staff. Because of how the company was structured, we had one for original regulations and one for Africa. The regulations in some of the African countries are not the same.

I would rate the product's scalability an eight out of ten. 

We have around eight people that directly work with the solution. They are four developers, two engineers, and two support staff. 

The scalability is good. I'd rate it five out of ten. It's deployed on the VM. You cannot scale up in some areas as you might hit a limit. Then, there are peak hours, and that might be different as well. You might hit a wall. 

Apigee is scalable and we have around one thousand customers currently.

The solution is scalable. 

The solution is highly scalable. I rate its scalability as a ten.

The solution is quite scalable. We can expand it if we need to.

We do not have plans to increase usage at this time.

Scalability is very good in the SaaS version. 

The scalability of the product is good. Our use case is right now is applied in only one environment. When we are about to go to production, we will probably do high-availability testing with a dual environment so we can come up with any potential scalability issues. But for now, we have not really touched that area in our testing.  

We do have a lot of people using Apigee already. This is the primary gateway for us to talk to external applications. I would say that services around 800- 900 applications which are using the gateways. That is also involving many teams and end-users who access those applications.  

The SaaS version of Apigee is quite scalable. The hybrid version is also scalable depending on your requirements.

Apigee is a scalable product.

Apigee has better scalability than WSA. 

This is a scalable solution. 

I think it depends on your license, but it's highly scalable.

It is scalable.

The scalability of Apigee is good.

Apigee will be implemented in over 100 hospitals.

It is scalable.

We have around four users.

There is a team of less than five people for deployment and maintenance.

As of now, we are going through a consolidation process within the company. Oliver Weyman is part of a larger group of companies. We are among the first ones to use it, but the plans for it are still not outlined for the next year, at least. This is something that we will finish figuring out within the next few quarters.

It has performed relatively well from a scalability perspective.

We have about 15 users in the company. They are a mixture of engineers, architects, and administrators, with the majority being architects.

Apigee's scalability is one of its main advantages.

The version I'm using isn't scalable. It's not the professional version. 

To date, our use cases have been limited so we haven't had significant scalability requirements. We have no plans for expanding the use of this product. 

This is a scalable solution.

With the SaaS model, scalability is there. 

It is suitable for large companies because it is a bit pricey. It is definitely not for small companies, but it might be suitable for medium companies.

We have built an API platform o over 2,000 different partners and all of them are using the gateways.

Apigee is a scalable solution.

We have not had to scale as of yet. Our license allows for 125 million messages and we have not yet reached that stage.

Our mother company has been using Apigee for maybe five years now. I talk with them about making assessments for selecting an API gateway solution. They didn't have any issues with scalability or monitoring. Apigee was perfect for them. We didn't face any issue with it in terms of scalability or even tenability. It's very easy to scale. 

As an integrator, we have about five different clients who use this solution. They have a different number of users.

The scalability is incredible. We make an average of 22 million API calls.

We have less than ten people who are developers.

We have plans to increase usage in the future.

There are close to 60 users at the moment. They are from the development team, the application team, and managers mostly.

We have not spoken to our clients about increasing usage or scaling the product. I am unsure of their future plans in that regard.

It is pretty scalable and we haven't reached any limits so far. We have thousands of users. There are a few hundred active internal users, a few thousand developers, and far more external users.

We have some very large customers that make a billion API calls a month and we have never heard any complaints about scalability. It's not an issue.

About half of our clients are mid-sized companies, with approximately 5,000 employees, whereas the other half is made up of companies that are bigger than that. 

Larger customers typically have 14-20 users on the product.

For large transactions, the commercial model is proving to be a constraint to some of our customers. For example, they're asking, when the scale grows, the commercial option becomes expensive. Some of our customers, for example, ask for an alternative approach due to the cost of the commercial model.

That said, you can scale. It's not a challenge in terms of doing it, it's just a challenge in terms of cost.

This is an easily scalable product based on your needs and loads on the system. Almost all components can be scaled horizontally which gives it an edge over other options available in this domain. However, you will have to make sure that you follow the guidelines and strict steps, as documented by Apigee, for adding or removing the nodes for a specific component.

No, we can add any quantity of all utilities such as users, API proxies, developers, their apps, etc.

I did not encounter any issues with scalability.

No issue with SaaS version.

I have found Apigee to be scalable.

We have more customers using Apigee than other API gateway solutions.

We have not had any issues with the product scalability.