---
title: "Should I use Entity Framework Core or Dapper for a new project?"  
description: "Should I use Entity Framework Core or Dapper for a new project?"  
author: "Ruslan Galiev"  
published: 2026-11-13  
updated: 2026-11-13  
canonical: https://www.mindstick.com/forum/163004/should-i-use-entity-framework-core-or-dapper-for-a-new-project  
category: "C# and .NET"  
tags: ["Entity Framework Core", "Dapper", "orm", ".net", "database access"]  
reading_time: 1 minute  

---

# Should I use Entity Framework Core or Dapper for a new project?

We are starting a new .NET 8 project with SQL Server. Some people on the team say EF Core is too slow and want Dapper. Which should we choose?

## Replies

### Reply by Jahnavi

Both are good, and they solve different problems.

- **EF Core** maps tables to classes, tracks changes, handles migrations and lets you write queries in LINQ. It saves a lot of code for normal create, read, update and delete work.
- **Dapper** is a thin layer over ADO.NET. You write the SQL, it maps results to objects quickly. You get full control and very little overhead, but you write more code.

For most business applications EF Core is fast enough, especially with AsNoTracking() on read queries. The usual slowness comes from loading too much data or from N+1 queries, not from EF itself.

A common and healthy mix is EF Core for writes and general queries, and Dapper (or raw SQL) for a few heavy reports or bulk operations. Measure with real data before deciding the team needs to avoid an ORM.


---

Original Source: https://www.mindstick.com/forum/163004/should-i-use-entity-framework-core-or-dapper-for-a-new-project

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.
