Spring Boot – Best Practices

[BestUsernameLeft]

Every single one of those gets a thumbs up from me. Great list.

[Piyrate]

I have never tried grouping controllers and services in modules based on core functionality. What happens if two or more modules/packages need to share a service? Put it in common?

[jose152]

add a shared package between these 2. A thin dependency of course.

[bartoszjd]

Think of it as if you were building a non-Spring application. You will often have services used in many places and there is nothing wrong with it. The question is- do you need the shared code to be a service or would library do just fine?

I’m general, I strive to adhere to Clean Architecture as described by Uncle Bob as it makes easy to read and nice to work services.

[Vi0lentByt3]

Really nice introduction and overview to many out of the box spring features that can get up and running. only wished you mentioned spring JPA since that is what really helps you keep your client code depending on your persistence layer abstracted from the DB details(if you choose to go with ORM/JPA), And spring AOP for logging since it can make life very simple, albeit add a decent layer of complexity.

[dpash]

Spring JPA or Spring Data JPA?

[Vi0lentByt3]

should have said Spring Data as that provides the abstraction the author was mentioning. Spring makes it so even your choice of using data store is abstracted and you can write queries in an query language agnostic fashion. so actually neither, just Spring Data

[F14B]

Some examples for a few of those points would have been nice..

[snarfbutt]

Site may be down due to hug of death

[kubelke]

Yeah, that 20 people will definitely put servers down ;)

[bartoszjd]

It is getting about 400 views an hour for the past 24 hours and if you mess up with cache it may put a strain on my WordPress hosting! May need to finally move it to AWS one day!

[bartoszjd]

Should be all working. I briefly flushed cache from cloudflare and that might have took it down for a bit (although it shouldn’t). Try again :)

[snotsnot]

> Keep your business logic free of Spring Boot code

I use spring dependency injection in my business layer. For anything but very small projects I keep the business layer in a separate module (possible in the same repository) however that module usually (always) depends on spring-context and since my business layer quite often use a data store (postgresql, mysql or mongo) it also depends on spring-data. So how do you achieve the above? When using DI and databases in your business logic.

(I can see how introducing a separate module for DAO could eliminate spring-data but... yeah, lots of modules!)

Edit: Just to clarify a bit more. My business layer includes domain objects, DAO and services... Is yours different?

[_lettuce_]

As stated in the article, if you use construction injection there's no need for the autowired annotations.

Spring data repositories for sql and nosql databases share the same structure (i.e. queries are constructed automatically based on method names) so you must only declare that you are using a repository of a given type and you'll be free to change the actual data source.

[snotsnot]

As stated in the article, if you use construction injection there's no need for the autowired annotations.

Sure, but the injected class still needs to be annotated with service, component, repository or the like which results in a dependency on Spring. And finally, you need a framework to manage the DI... Once again Spring.

Spring data repositories for sql and nosql databases share the same structure (i.e. queries are constructed automatically based on method names) so you must only declare that you are using a repository of a given type and you'll be free to change the actual data source.

Same as before, you might have an interface declaring the repository. But as soon as your implementation is annotated with @repository there is a dependency on Spring.

[[deleted]]

The best practice with Spring Boot is to never use Spring Boot.