FINDING 01·Backend developers and .NET/web application developers·2 sources
ORM performance overhead vs. raw SQL
A recurring frustration across multiple eras is that full-featured ORMs introduce significant performance overhead compared to raw or inline SQL, making them unsuitable for projects where query speed is critical. This pain appears in both older (2012) and more recent (2023) discussions, suggesting it remains a live concern.
Source
“A large feature-rich ORM library (Subsonic) was added to the project awhile back, which it turns out was just too much. It's too big, there's too many parts, there's too much overhead. Some Collections that are generated by Subsonic take >1min to create, whereas raw inline queries (bad I know) that accomplish the same take ~2s.”
Source
“We migrated to SQL. Our biggest learning? Don't use Prisma ORM”
FINDING 02·Small-team or indie developers building modest web or desktop applications·2 sources
ORM complexity and steep learning curve for small or simple projects
Developers on small-scale projects find that full-featured ORMs generate excessive boilerplate code, introduce unnecessary complexity, and have steep learning curves that are disproportionate to the project's needs.
Source
“I've looked at orm tools but in my opinion they generate a lot of code and i do not know if it's necessary.”
Source
“NHibernate and other ORM tools are just too big, with way too many features that will never be used. The scope of these projects will never get huge either.”
FINDING 03·Java developers transitioning from .NET or working with existing database schemas·1 source
Lack of database-first ORM support in Java ecosystems
As of 2025, Java developers familiar with Entity Framework's database-first workflow (generating model classes from an existing schema) find it unclear or difficult to replicate this approach using Hibernate or JPA, creating friction when migrating from C# or working with pre-existing schemas.
Source
“I'm used to working with a Database First approach in C#. I design my database schema (often with MySQL Workbench) and do a forward engineering, then generate my C# models using Entity Framework's. This way, I get classes matching my tables automatically and can use LINQ to manipulate data without writing all the objects manually. I'm looking for something similar in Java — a tool or framework that can generate Java classes from an existing database and let me easily work with data through an ORM. Does Hibernate or JPA support this?”
FINDING 04·Backend developers working on multi-project or team-based SQL-first architectures·2 sources
Difficulty keeping database schema and application model in sync without an ORM
When teams opt out of ORMs and use plain SQL, keeping the database schema synchronized with backend code across multiple developers and repositories becomes a significant workflow challenge, especially for multi-project setups sharing a single database.
Source
“Now I'm creating multiple projects relying on one database type only and plain SQL has to be used. I would like to know about the best practises to deal with the additional 'database project'... The problem that comes to my mind is that when working with many developers on the database and backend project how to keep both projects synchronized?”
Source
“Generally, I have a question about ORM(s), and the best way for managing enterprise/small applications' database schema and model (Actually, to keep application model and database schema sync always) Is this a good way to create database schema from application models or first creating database schema and then, create application model from it?”
FINDING 05·Enterprise .NET developers maintaining legacy Oracle/SQL Server systems·2 sources
Poor ORM support for legacy databases with stored procedures and non-standard schemas
Developers working with legacy Oracle or SQL Server databases — featuring stored procedures, composite keys, no ID fields, and tightly DBA-controlled schemas — find that mainstream ORMs like NHibernate do not integrate well, forcing them to seek niche or custom solutions.
Source
“I have some experience with ORM tools like nHibernate but after playing around with it a bit in our environment it doesn't really seem to be the best option for working with a legacy database like this. Does anyone know of a good tool that will allow stored procedures to be called easily and map the results into sets/collections of objects?”
Source
“All database access is done using stored procedures and no SQL is allowed in the web services... Also, allowing the tool to create any of the SQL is also out the question. My question is: Given these constraints, which of these tools would allow the best integration for this sort of environment?”
FINDING 06·Enterprise database architects and .NET developers on large Oracle systems·1 source
ORM scalability issues with very large database schemas
ORMs struggle or become unresponsive when mapping against databases with thousands of tables, making them impractical for large enterprise Oracle environments. This was reported in 2009 and reflects a structural limitation of code-generation-based ORM tooling.
Source
“I am looking for the best .Net ORM tool that would work with Oracle and SQL Server 2005. We have an Oracle database with around 4000 tables. I tried TierDeveloper and Codesmith and they are not responding when I try to map objects with my Oracle DB.”