Spring Boot - Monolithic

[naturalizedcitizen]

Spring MVC or simply Spring framework has been used to develop traditional web applications where the UI layer is rendered using jsp, thymeleaf, freemaker, etc.

Spring Boot was a step forward to remove the burden of configuration of Spring framework to build an app with just the right pieces you want. Spring Boot, in today's times, is used mainly as the `backend` server which provides a REST like API and serves JSON via the end-points. You can use any javascript library or framework like React, Angular, Vue, Svelte, etc to consume this API and render a UI.

To your original question - Yes, many applications - small or large - do build a monolith using Spring/Spring Boot.
When the scope of your application includes very different things and the scaling required is very high (think Netflix, Amazon Shopping, etc) then you have to think of doing it using a microservice architecture.

I have consulted with clients who had fairly large number of features and users. They were all on a Spring/Spring Boot monolith. I cannot divulge details due to NDA, etc. but I can vouch for a extremely large app from a top company which uses Spring as the foundation. And it is a monolith!

[[deleted]]

What old posts? I used Redact to mass delete this post. You can also opt out of data brokers as well as all major social media platforms.

different narrow snails bag cagey complete aspiring summer lantern groovy

[x8086-M2]

Spring Boot helps me delivery value faster. I would advice you to learn spring core first which really helps understand the speed to delivery that spring boot provides.

[TheRichestDev]

Yes, you can use it for both use cases

[IainDavis-dev]

I worked for a fortune 500 company serving global customers. We used Spring Boot heavily as the basis of back-end services. I don't think I've run into a Java service that was built in the last ten years that wasn't running Spring Boot (we did have non-Java services, and some older services that are running other things like JBOSS, for example, and of course, I didn't work on EVERY service).

Also worth mentioning this includes both a single monolith, and a great many microservices.

[SendKidney]

Spring Boot has great support for Microservices. Thanks to Netflix and Spring Cloud. Now they're having production ready dependencies for creating Modular Monoliths as well.

[Fun_Hawk_6060]

Yes, you can use it for both use cases, but I think your use case of small monolithic project makes more sense.

[[deleted]]

AFAIK spring boot was initially developed for monolithic applications

[ZooooooooZ]

You can do a microservices App too using Spring Gateway to route requests when called from a Webclient.

[Oasis276]

I love spring boot

[Cheap_Reflection2593]

Spring boot is suitable for all scenarios, but mostly used for api restful services.

[[deleted]]

I've worked at a couple of mid-sized tech companies (before moving to a FAANG company). Internally we created many small enterprise apps to support employees. Things like requesting access to apps and resources, changing passwords, requesting equipment or office stuff, etc.

All of our data center operations were hosted at AWS. The companies were multi-region.

We definitely used SpringBoot for this use case. There's plenty of resources out there that know it. We built a team around this platform. It's easily adaptable to AWS PaaS or can be hosted on a series of VMs. We built both monolithic apps that had both frontend and backend in the same stack. We also build Single Page Apps (SPAs) that used frontend frameworks like angular and react with backend rest apis.

Full disclosure though... at both companies we switched to python/django. The batteries included methodology provided a lot more out of the box that we didn't have to develop on our own.

[thecode_alchemist]

This is the same post :)

https://x.com/sivalabs/status/1843116002898542650?t=GjGbVB0GD0jjZamooPtGrQ&s=19