There are different business units that use it. They have a concept of a tenant. Therefore, we have a cluster running around multiples. We have two clusters running, one in non-production and one in production. Production is mainly for testing QA, and production is production. However, then different organizations have different logging. As a developer, we are about six people. The Linux team will have about 15 people. VMware will have a lot of users in general.

It's actually very easy to add a node and scale the ports in different nodes. It does it automatically since it's managed by Kubernetes.

We’re moving off of it. However, it will take a while. The support ends in 2024. Since we're starting development with Resolve, obviously, the time to migrate all the stuff we've done from one from CloudCenter to the other tool will take some time, so we will still be running it.

Various tool sets and products are available to scale the solution. 

Scalability is actually pretty good. When we started using the product, we told them we would need a DR option and so they designed the out-of-region DR option for their database for us to be able to point our database. And so from a scalability perspective, it's very interesting. Now as of CloudCenter 5, they've reduced the complexity significantly inside the platform, so it's not Kubernetes-based and it's cogs, you don't necessarily need a per cloud Orchestrator like you needed before to deploy stuff based on customer feedback. And we're obviously not the only ones, but previously you needed to have some VM running into different clouds and they tried to reduce that. So we don't spend money just for being able to meet in the cloud. There are different components. As of CloudCenter Suite version 5, the scalability is based on Kubernetes, so if you need more compute in the workload manager, they'll just spawn more pods for the Action Orchestrator. So typically anything you would see with the containers is something that you'd be able to feel as to how scalable it is because typically the limit is how much compute you're going to be giving to your actual deployment. If you have the pleasure of installing the product, you have to make a choice at the beginning. The size of the workers and masters you want to give. That's typically where you do your first choice afterward. It's really based on the capacity of either your VMware Endpoint or other cloud endpoints and how much you can consume on their scalability.

I rate the product’s scalability a nine out of ten.

There have been no limits as to what I know and what we have reached, as of today. I haven't seen a ceiling on its ability to expand. The scalability is nice.

All the users on our end are DevOps and we are the admins of the VMware identity infrastructure. We have roughly 50 to 60 users actively using it at any given time.

I would rate the product's scalability a nine out of ten. My company has 300 users for the product. 

The scalability is excellent. Cisco has a reputation for being a very easy product to scale. If a company needs to expand, it should be able to do so without issue.

We tend to work with large-scale organizations such as banks, service providers, and companies in the finance sector. I would estimate we have no more than five customers, however, they are all sizable.

We suspect that our clients will increase usage in the future. Many are developing cloud centers like this.

Cisco CloudCenter's scalability is good.