Member-only story

Why the Industry is Moving Back to JDBC from JPA — This one will hurt a lot of developers.

3 min read1 day ago

I recently attended a Spring event where experts who work directly with Oliver Drotbohm — a key figure in the Spring ecosystem — discussed an interesting trend: many teams, including those at Broadcom, are moving away from JPA (Hibernate) and switching back to JDBC.

This shift is gaining traction across various industries, especially in high-performance applications.

Photo by The Matter of Food on Unsplash

For years, JPA has been the go-to abstraction for database interactions in Spring applications, offering a streamlined approach to handling persistence. However, the overhead, performance bottlenecks, and lack of fine-grained controlare prompting developers to reconsider its use.

Let’s explore why this transition is happening.

The Core Reasons Behind the Shift

1. Performance Bottlenecks in JPA (Hibernate)

JPA introduces an abstraction layer over SQL, which can lead to serious performance issues:

I disagree with some of the premise here. Using straight JDBC does allow you to optimize queries substantially and that’s a huge gain, but it is terrible for maintainability because your code becomes tightly coupled to the database. When you make…

Why the Industry is Moving Back to JDBC from JPA — This one will hurt a lot of developers.

For years, JPA has been the go-to abstraction for database interactions in Spring applications, offering a streamlined approach to handling persistence. However, the overhead, performance bottlenecks, and lack of fine-grained controlare prompting developers to reconsider its use.

Let’s explore why this transition is happening.

The Core Reasons Behind the Shift

1. Performance Bottlenecks in JPA (Hibernate)

Create an account to read the full story.

Written by Full Stack Developer

Responses (10)

More from Full Stack Developer

How I Started Doing ‘Null Pointer Exception’ Checks using just One Word in Java

I have discussed 2 one-word options for replacing boiler plate code to perfome null check in your application. I hope this helps you!!!!

BindingResult — An Interface in Spring Framewr(A feature many developers don’t use)

Instead of validating Dto fields one-by-one, with BindingResult, check ’em all and store them in one place :)

@RequestParam vs @QueryParam vs @PathParam vs @PathVariable in REST

Pretty confusing if you don’t know this simple fact.

Springboot 3 and Springdoc Openapi 3, Swagger Impl: “No Operation Defined In Spec” Error

Not seeing your REST API, even though you have defined one? Solve this error completely with these sure shot tips.

Recommended from Medium

I Thought I Knew Java Streams Until I Saw This😮

I still remember the day I confidently wrote a piece of code using Java Streams, thinking I had fully mastered them. Everything looked…

Java’s Funeral Has Been Announced….☠️💻

Oh, Java is outdated! Java is too verbose! No one uses Java anymore!

Why Spring Ditched @Autowired: The Surprising Alternatives You’ll Wish You Knew Sooner

Exploring the shift away from @Autowired in Spring and embracing cleaner, modern dependency injection alternatives

Top 10 Java Optimization Techniques for High-Performance Code

Java applications can become slow due to inefficient memory usage, unnecessary object creation, or poor algorithm choices. Here are 10…

Multi-Tenant Architecture using SpringBoot and PostgreSQL

Multi-Tenancy in Spring Boot Using PostgreSQL (Schema-per-Tenant)

10 Advanced Coding Practices Java Seniors Live By

Discover the battle-tested coding practices that separate senior Java developers from the rest. This advanced guide reveals the techniques…