Johannes RabauerDec 28
Recently I worked with @hibernate in a slightly larger backend project.
Pretty quickly I realized the real problem was not performance.
It was that I did not fully understand what Hibernate was doing.
#Java #BackendDevelopment
Show threadJohannes RabauerDec 28
As queries became more complex, I had to reason about
Java entities
Hibernate mappings and fetch behavior
Generated SQL
Database execution
All at the same time.
Show threadJohannes RabauerDec 28
I ended up refactoring large parts of the schema and reworking Flyway migrations just to get queries into a reasonable shape.
The abstraction did not remove complexity. It hid it.
Show threadJohannes Rabauer
That is when I started looking into @jOOQ.
It requires solid SQL knowledge and more explicit DTOs.
But it is honest about what it does.
You always see the query you are actually running.
#SQL #jOOQ
Dec 28 at 6:45pmWeb
Show threadJohannes RabauerDec 28
On Tuesday 30 December 2025 at 20:00 CEST
I will do a live coding stream comparing both approaches.
https://youtube.com/live/3tnpb88UaeA?feature=share
#LiveCoding #SoftwareEngineering
One backend twice - Hibernate vs jOOQ on real code

YouTube
Show threadJohannes RabauerDec 28
One backend implemented twice
Same API
Same database
One version with Hibernate
One version with jOOQ
Show threadJohannes RabauerDec 28

We will look at real code, generated SQL, and how complexity evolves as requirements grow.

If you care about backend systems beyond CRUD, join me.