Who is using Spring Boot?

Been using Spring Boot for side projects as well as for my 9-to-5 job. Use it with Thymeleaf because as many have said here, it's better to use what you know best.

As others have mentioned, one of the struggles is to find a cheap host to deploy the app. But there are options out there.

The second struggle I have is to find SaaS projects developed entirely in Java (What I mean by "entirely" is using Java in the back and front-end, with frameworks like Thymeleaf or even JSP.), developed by solo devs.

If there are quite a few of us, maybe we should consider creating a group chat or some communication channel to share experiences.

What do you guys think?

I have been using SBT on big projects. On side projects I still try to use other tech that might be cheaper to host until the project is profitable. If you know it will make money it is worth doing it on SBT as it is the best framework our there.

I have been using Spring Boot for over 6 years now. It's a good tool in your arsenal given most enterprises live by it. Kotlin's support is a big win for developers like me. At my workplace, most of the projects I worked on uses spring boot and React or Vuejs for frontend. For my side projects, I experiment with different languages/tools. Mainly django, nodejs on the API side of it. some times firebase/firestore when I take up some freelance work to get the MVP up and running. Right tool for the job

I am using Spring Boot. I built rentersvoices.com using Spring Boot, Spring Security and Thymeleaf components.

Spring Boot is very easy to use framework if you have used it before.

I usually use Spring Boot as I have been working with Spring for a long time. Even wrote books on it. Super productive and easy to code an api fast. The only downside for me is the hosting for side-projects. Sure, Heroku is fine but it might get expensive with a few apps. If they all make money, it doea not matter really.

Use whatever you are productive with.

I've always avoided using Spring Boot for my own projects favoring the use of native servlets and Jersey web services. It's entirely a matter of preference but there is far too much automagic configuration for my taste in a Spring Boot project. While I would absolutely recommend it for a development team, I've found that I spend as much time looking for configuration parameters to reset or default behaviors to override as I save using what comes out-of-the-box with Spring Boot.

For a development team, however, the fact that there is a "Spring Boot" way of doing things means that the development team has a relatively standard approach to follow. This is especially handy when the team is relatively new to application development.

I use it for work (with JHipster) but use NodeJS for a side project I am building right now.

It's my go to. So easy to set up, and enough scope for more stuff once you need to scale up in size and complexity.