ST
/ORM
Kotlin 2.0–2.4
AI
Tutorials
Examples
Comparison
Benchmarks
Blog
Documentation
GitHub
Get started
Ideas behind
the framework.
Notes on the design decisions in ST/ORM and on how it works inside.
All
12
Origin
1
Design
3
Hibernate
2
SQL
1
Internals
2
Comparison
1
Opinion
2
//
Articles
Why ST/ORM is built the way it is, and what that means for the code you write.
Why we built ST/ORM
→
If you have worked with JPA and Hibernate long enough, you probably know the feeling. Most of the time things are fine, then the model and the codebase grow and there is some drama. When we got the opportunity to start over, we took it, and that is where this story starts.
September 2, 2025
Origin
A first-principles approach to your data layer
→
Describe a table in its most concise form and you get the type that carries your data, which is also the contract for querying the entire relation graph.
September 30, 2025
Design
Entities are just data
→
An entity in ST/ORM is a plain record, a value with no session and no hidden state. This post covers what that gets you across an application, and how dirty checking and lazy loading still work.
October 28, 2025
Design
LazyInitializationException, and what it's telling you
→
The most-googled Hibernate error comes from a lazy load that runs after the session has closed, rather than from a bug in your code. Value entities cannot throw it.
November 25, 2025
Hibernate
The N+1 problem, and loading you can see
→
A fetch clause fixes N+1 only until the next query forgets it. ST/ORM makes loading a decision the code shows you, and one you can assert in a test.
December 16, 2025
Hibernate
Stop hiding my SQL
→
SQL is the interface every database and every backend engineer already shares. We think it should be typed and kept in view, instead of replaced by a second query language.
January 20, 2026
SQL
Three abstractions and nothing else
→
ST/ORM has three concepts: Entity, Repository and SQL Template. We kept the model that small so you can hold all of it in your head.
February 17, 2026
Design
The static metamodel
→
Each entity gets a companion class generated at compile time, which type-checks column and path references and lets queries and hydration run on generated code instead of reflection.
March 3, 2026
Internals
Dirty checking without proxies
→
To write only the columns that changed, ST/ORM compares the value before with the value after. No bytecode enhancement or session-bound proxy is involved.
March 17, 2026
Internals
Why we didn't choose Exposed
→
We build in Kotlin, and JetBrains Exposed is excellent at modeling a database, so building ST/ORM on top of it was a fair question. ST/ORM draws the boundary in a different place: the model stays in the database, and application code works with plain, typed records.
April 14, 2026
Comparison
Why shouldn't we use an ORM?
→
The strongest arguments against ORMs turn out to be arguments against ORMs that hide SQL, and an ORM that keeps SQL in view answers most of them.
June 9, 2026
Opinion
The M in ORM stands for …
→
Everyone says the M stands for mapping. Look at what the tools carrying the name actually do and a lot of it is management. We think you should be able to have the mapping without the management.
July 24, 2026
Opinion