DEV Community

loading...

Discussion on: Dapper.NET: Handling Multiple Resultsets

Collapse
yorek profile image
Davide Mauri Author

Hi Dapper is surely faster (you can check the performances here: github.com/StackExchange/Dapper#pe...) but is not necessarely better than EF Core. EF Core is a full fledged ORM, with a tons of features that Dapper doesn't have. On the other hand if prefer direct control on what SQL code is executed, Dapper is a great micro-ORM that doesn't add almost any overhead and thus is really fast. It just removes the plumbing code. Sure, you can use Stored Procedure with Dapper. If you just want to call Stored Procedures, I would definitely choose Dapper. In the first article of the series (dev.to/yorek/get-started-with-dapp...), there is a section on Stored Procedures and Parameters. Give it a read to have the complete picture.

Collapse
shaijut profile image
Shaiju T

Thanks, What are the reasons to prefer Dapper.NET over ADO.NET ? I think ADO.NET should be more faster than Dapper.NET and Entity Framework.

Also I don't like to see SQL select statements inside Application code. So I create ADO.NET repository with Stored Procedures for SELECT. I think it's more clean and maintainable.

Thread Thread
yorek profile image
Davide Mauri Author

Dapper.NET extends ADO.NET. Great, you're following the best practices already, by separating SQL code from .NET code and using Stored Procedures.