Spring Boot is a Java Framework, and it offers dependency management for Maven and Gradle, but we use it as a Maven project. We're a massive bank, and I estimate that 95 percent of Java projects use the Spring Boot Framework. It's upwards of 40,000 users.

Spring Boot is used for microservices and web apps.

Spring Boot is a highly modular and versatile framework with excellent inversion of control and dependency management features. It also implements the popular MVC (Model-View-Controller) pattern and offers other useful design patterns, such as the active system via Spring Security. The framework is excellent for developing black feed applications, and developer tools and monitoring systems are also available. Additionally, Spring Cloud is a fantastic tool for writing code for cloud platforms like GCP Cloudgram, as it facilitates the rapid development of APIs.

The use cases depend on the domain I require it for. Sometimes its for the banking domain and sometimes for health.

We use the solution to build microservice architecture. It helps us expose microservices to REST API or similar messaging applications to provide a communication bridge.

We started using Spring Boot because we wanted to implement the microservice- based architecture. We selected Spring Boot to develop our services using the Spring framework.

We deploy the solution on-premises and on the cloud. On the cloud, we deploy it through Azure and AWS. We've also deployed it on PCF, which is a cloud agnostic platform.

We're using version 2.x.

There are 130 members in my organization who use String Boot. These users include the development team, the testing team, the administration team, and the deployment team.

We use Spring Boot to create different microservices. The configuration is very easy. We also make use of the in-built server. Spring Boot Two has reactive programming and that is valuable for microservices development. We have more than 1,000 users supported by Spring Boot. 

We use this solution on-premise as well as on the public cloud.

We use the solution to manage our microservices. It helped us develop a web application portal for a financial company.

We use this solution for web applications and to handle data relevant to our customers. 

It's a framework that is very easy to access and easy to configure. It's inbuilt to the Apache Tomcat server, and it's very lightweight. 

We use Spring Boot to build our own microservices as per our platform requirements. We build everything from scratch. It is easy for developers to learn how to use and to start building. We have approximately 100 people in our team using it. 

I primarily rely on Spring Boot as the core microservices framework, used for creating myriad solutions for health care and for the financial services industries. Environments change, depending on client commitments and budgets, but Spring Boot remains as the successful nexus for all development.

I have used it for both SQL and NoSQL solutions, including both caching and non-caching environments. With over 20 Spring modules to select for possible augmentation of the basic Spring Boot platform, there is nearly always a solution available.

In cases, where some additional, narrow functionality is still lacking, many existing solutions can be integrated into the Spring Boot Java framework, even if that functionality is not part of an official Spring Boot add-on module.

My team uses Spring Boot to build APIs. We're running Spring Boot for 90% to 95% of our ecosystem. When you talk about the Java system, Spring Boot is the only framework we're using right now.

We primarily used the solution for web applications. 

The solution is mainly used for microservices. It's a Java solution. 

I used Spring Boot to create a prototype for a banking solution. I developed two microservices, one for ATMs and the other for the backend. I used Spring Boot with the microservices architecture. I also wrote an application to calculate discount strategies or sales systems for a backend website.

We use a variety of actuators. We have also been working with a Spring MVC as a plugin, so we Hibernate ORM like the one where we connect to the database. We use it a lot, and Spring Boot provides interfaces like run command line runner replication. The configuration setup in Spring Boot is pretty simplified compared to Hibernate ORM.

We are using Spring Boot to create services.

We use Spring Boot for microservices, but for the logistic version. We also use the solution for traditional banking purposes.

It's being used for the front-end web portion of our application.

We use the solution to run microservices on an Azure platform. Our UI is on Angular, and Spring Boot is our backend. We have connections with Kafka Topics and some IBM backend tools, and Spring Boot is sufficient to play the part of the orchestration layer.

We host a web app where we have different APIs of the e-commerce marketplace and we use Spring Boot on the backend.

I work for customers in several industries and I mainly develop API and support applications and innovation with them, depending on the customer needs. I work in healthcare, logistics, and manufacturing.

I primarily use the solution for web applications. 

We use this solution for human resources applications. 

The big thing in Spring Boot is that you don't need to make many manual configurations to set up some of the basic things I analyze. If you use Spring Core and want a JDBC connection, you need to consider a lot of XML files to have the JDBC connection done. In Spring Boots, it is simple to have the JDBC connection since the basic functions can be achieved with minimal codes or minimal configurations, making it a very powerful tool. There is not much custom configuration needed in Spring Boot.

I primarily use the solution at the point of sale. It covers inventory management at multiple locations and reports as well. 

Spring Boot is deployed on a Azure Kubernetes container.

If I have to interact with a core banking system or any other application, I use  Spring Boot.

We are using Spring Boot for many use cases.

Our use of this solution is related to creating microservices, based on microservices architecture that we're implementing now.

My primary use case is to develop APIs used by single-page applications. It's almost exclusively for web applications and sometimes for communication between micro services, meaning two Spring Boot apps talking to each other. I develop API and the processes, using open API to define before developing them. With Spring Boot we generate the code and we serve the API's to this single-page application or other micro services. I use it almost every day. It's open source, so we don't have any partnership with them, we're a customer. I'm a software engineer. 

We are using this solution for various in-house applications and products.

We are using the latest version of Java Spring Boot. We can just start with the application within a day. When we start developing we can just start up the application development immediately and work for like four or five hours. We are using it for logistics companies and will be logging thousands of users. Companies of three thousand to four thousand users are what we are using it for.

I use Spring Boot to develop microservices.

We primarily use the solution for building websites and the backend.

I'm the CEO of our company and a user of Spring Boot. I use the product on a daily basis for business applications. It's great because it simplifies development. Together with MyBatis, they make a beautiful pair for Java development. I'll be developing with Spring Boot in the future.

I have 12 developers using Spring Boot in my organization. There are currently two teams in my company: one for the web version, another for the desktop version.

We primarily use the solution for building applications.