It is an operator model. So, we have only five to six users in our organization. I rate its scalability an eight out of ten.

In my experience, I have found this solution is best suited for small integrations.

It's great because it works with Kubernetes and can be scaled.

In our organization, we have approximately 500 users who use this solution on a daily basis, primarily because we have some public sites that are linked to this.

Users create accounts and use them to log in.

The scalability is there. Currently we are able to support more than one hundred thousand users, and we are able to manage them using LDAP.

We have multiple projects where this solution is used. One of these projects has thirty internal users, and the external users are their customers. It is a huge customer base.

Another one of our projects has approximately one hundred users, which will be more than ten thousand customers.

Generally, there are two kinds of projects. The first I call "light", where the customers are the end users. This makes for a very large number of users. The second type of project is an operational team, where there are approximately one hundred users, or real-time operation team members. Their customers will total more than ten thousand.

We do have plans to increase our number of clients.

Scalability is really something we watch out for - especially in relation to the number of cores. Not only with the WSO2 product, but any product that you take on now. The number of transactions depends on the core volume. You need to understand what processor and how much CPU you are using as well as how many cores and how much memory. That said, from a scalability perspective, it's my understanding that it is very easy to scale.

We have not explored this solution's scalability yet.