Spring + hibernate versus Spring Data JPA: Are they different?

when you talk about spring + hibernate

1. If you read hibernate alone, you would understand it uses mapping(which basically configuration for mapping of pojo with database relations) and configuration(configuration specific to database like driver class, url, username, password, dialect etc.).
2. So now if you want to use read, write, update etc. you have to get hibernatesessionfactory, open transaction and commit. Lot of pre and post work for each operation.
3. When you integrate hibernate with spring, spring uses this configuration and keep it in application context, and provide wrapper which is hibernatetemplate which internally using hibernatesessionfactory. So you dont need to care much about pre and post code while doing these operations.
4. It also provided caching(first and second level cache) to improve performance.
5. And also give you to work with HQL which is independent of database.It uses database dialect to generate database specific sql.

Now lets talk about spring + data jpa

1. it comes with base repository interfaces(from spring data common, spring jpa)
2. So suppose you are interested in doing crud operation, just extend crud repository, and spring will inject its implementation at run time.
3. Lets say you want to define common method for your application, you can do that by creating new repository interface which extends Repository interface. And can use this across the application.
4. It also provide query methods which allow you to use native sql or jpql.

Spring-data-jpa, as you're saying, offers more that just the classical Spring-JPA integration. With JPA/Hibernate integration, you get mainly

• declarative transaction management using JPA/Hibernate transactions
• exception translation
• the JPA EntityManager or the Hibernate SessionFactory as injectable beans

With Spring-data-jpa, you get all that, plus (among other things)

• interface-only repositories, using method names to infer queries automatically
• @Query annotation to define the query that an interface method should return
• automatic handling of Pageable queries
• base classes for standard crud repositories

This is just a tiny introduction. For more help, read the documentation.

Spring Data JPA is not a JPA provider. It is a library/framework that adds an extra layer of abstraction on the top of our JPA provider (like Hibernate).

So you can't use Spring Data without a JPA provider like Hibernate, EclipseLink, etc.

I find this link helpful:

JPA is the Java Persistence API, which is Java's standard API for object-relational mapping.

JPA is only an specification - you need an implementation of it to be able to use it. Hibernate is one of the most well-known and most used implementations of JPA, but there are others, such as EclipseLink JPA.

The Spring Framework is a large framework to help you write enterprise-grade software easier. It contains support for many Java technologies, including JPA.

The Spring Framework consists of a collection of projects, and one of these projects is Spring Data.

The goal of Spring Data is to make it easier to work with different kinds of databases, from traditional relational databases to NoSQL databases. Spring Data supports JPA via the Spring Data JPA subproject.

To write a program that uses JPA, you need at least a JPA implementation, such as Hibernate.

If you are using the Spring Framework for your application, you will most likely want to use Spring Data JPA together with Hibernate.