Home/ Questions/Q 6845533
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T00:30:45+00:00

We are currently using Spring MVC to implement REST web services. We now want

  • 0

We are currently using Spring MVC to implement REST web services. We now want to implement some kind of data persistence, and I am looking at what the options are. Spring Transactions + Hibernate + MySQL seem to be a quite popular approach, but every single blog / tutorial I have looked at does it differently.

Can anyone guide me to what could be considered the “best practice” for data persistance using Spring? I would like to make it annotation based, as this seems more natural and maintainable to me.

But now in some places I have read that HibernateTemplate should not be used anymore. And some people use the *Dao interface and *DaoImpl with @Repository approach, while others use *Service with @Service approach.

Thanks in advance for any advice.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    HibernateTemplate is indeed not very useful, and the Spring doc advises considering not to use it anymore.

    @Repository and @Service basically do the same thing, except (AFAIK) two things:

    • @Repository makes it clear that the service is a DAO, and not a business service
    • exceptions thrown from an @Repository annotated service are translated to Spring’s persistence exception classes. This means that you won’t get Hibernate exceptions, but Spring exceptions wrapping Hibernate ones.
    • 0