Spring Boot is highly scalable. It has scaled up a lot compared to the earlier versions. 

Scalability is a crucial factor, especially as we move towards developing microservices-based systems. In this new model, the responsibility of each service is significantly reduced. Unlike in the past where multi-threading and application handling required more attention, today's focus is more on scaling up with particle scaling as the norm.

Horizontal scalability is the norm today. With this approach, we can achieve resilience and deploy multiple instances of a system, coordinating them to ensure proper request and response handling. This strategy is highly scalable and offers increased flexibility.

All of our Java developers are using Spring Boot.

I rate the scalability of Spring Boot an eight out of ten.

It is a scalable solution. I rate the stability nine out of ten.

It is a very scalable solution. I rate its scalability as a nine.

I would rate the scalability as seven out of ten. 

Spring Boot is scalable at an infrastructure level, meaning that we can increase the number of instances based on the load on the particular service or particular application. It's infrastructure-level scalability. There is also inbuilt scalability of the service. For example, Web Flex and Vert.x have inbuilt scalability, meaning there is scaling of service inside the service, not outside the service, such as infrastructure. The design level scalability should be implemented first.

This is a scalable solution. 

We have more than 100 backend developers utilizing the solution. It is scalable, but it depends on the infrastructure that you are using. Also, it requires specific knowledge of managing loads and deployment of microservice applications.

This is a scalable solution. We have an application that consumes around 500,000 messages per second and it's handling it quite well. This does depend on the capabilities of your hardware. 

This is a scalable solution. 

I rate the solution's scalability a ten.

Spring Boot scales well. Care must be taken if any state is to be maintained since maximum scalability would be associated with a singleton instance of the application.

Spring Boot is a highly scalable solution. Around 200 to 250 users are using Spring Boot in our organization.

The solution is scalable. It can extend well. 

We had about 4,000 or 5,000 users on the solution.

We have 16 banks with us, and we use Spring Boot in some capacity in them all. 

It's a scalable solution. 

Except for Spring Reactive, the other tools and technology stacks in Spring Boot don't offer scalability. 

It is scalable. We are currently serving around 10000 users.

Spring Boot is meant to be scalable. We use microservice architecture, which is tightly coupled with our Kubernetes cluster. You have your microservices with the default one or three ports, and based on the traffic, you can scale up your ports. The scalability of Spring Boot is very good.

Most of our whole company is using this solution, which is over 10,000 people.

Spring Boot is a scalable tool. For example, in some microservices, you can just scale down if not used in most cases. For other micro solutions, you can bring up in the RAM space or in cluster mode. If you need more people to use Spring Boot, you can scale it, with no issues.

I haven't tried to scale the solution. I'm not sure how well it would scale, having never tried. 

We mostly have software developers using the solution. It's not meant for everyone in the company to access. We just have small teams on it. 

The product is scalable, providing the proper infrastructure is in place. If we have the resources, we could have 100 instances of the solution running, and that would be fine if the load were balanced. We use Spring Boot bank-wide, with about 300 developers in total.

I give the scalability an eight out of ten.

We have 20 people using the solution in our organization.

It is scalable. It is a cloud-native technology. Therefore, it fits with most cloud environments and container platforms. There are not many problems in scaling it. The only problem is if it's not compiled natively, it's slow. That said, this is a Java problem, not a framework problem, let's say.

I'm not sure how many people use the solution within our organization, or how often. However, my understanding is that it is widely used. 

Considering that If we are using the correct microservices and architecture using Spring Boot, I rate the solution scalability a nine or ten out of ten.

If you are using a monolithic architecture with Java Spring Boot, then the tool will not provide enough scope for scalability. With microservices, you can deploy the tool with a lot of functions and make it scalable.

Around 50 people use the solution in my company, but there are a total of 80 people who know Spring Boot.

The solution is very scalable. 

The scalability of Spring Boot is good.

We have more than 1,000 users using this solution.

The solution is scalable.

It's a scalable solution.

Scalability depends on how and what features you use. If you have to scale a stateless API application, it's easy because you can scale it horizontally, ensuring that all the shared resources are available and that if the nodes need to talk to each other, they can. Spring Cloud helps and it's well supported and documented.

Spring Boot is scalable.

I have a team of 50, who are using this solution. The organization has approximately 120 users.

We plan to continue our usage with Spring Boot.

One of the best advantages of Spring Boot is the scalability. You don't have to worry about it. You can deploy an application like in a service. If I want to have a separate application, or if you want to go with a business logic application, I would tend to go with the single application for the instance. So when I just want to increase the business logic application resources I can just scale up the service. I don't have to scale the whole application. That's monolithic. You can deploy an application individually or have it as a single application.

I don't really use the solution to scale. I've never tried to expand it. 

As a Java program, it's very scalable.

The solution is scalable.

The scalability on-premises is limited as you are dealing with hardware. However, in the cloud, scalability is quite good. If a user needs to scale the solution they definitely need to consider deploying the cloud version.

We have about 400 users on the solution on the on-premises deployment model.

We have plans to increase the usage of the solution in the future.