For new projects, do you prefer EF, ADO, Dapper or something else?

This page summarizes the projects mentioned and recommended in the original post on /r/dotnet

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • SqlMarshal

    Generates data access using stored procedures

  • After writing SQL, I prefer to interface with dotnet code via auto-generated types. This gives type safety compared to Dapper and manually generated ADO. I just posted an issue giving some libraries which do this here: https://github.com/kant2002/SqlMarshal/issues/4

  • NReco.Data

    Fast DB-independent DAL for .NET Core: abstract queries, SQL commands builder, schema-less data access, POCO mapping (micro-ORM). (by nreco)

  • We use https://github.com/nreco/data in our products, similar to Dapper but with built-in SQL generation for CRUD-queries (it is very easy to compose filters in run-time) + hand-written SQL may be concentrated in one place (app-level 'dataviews').

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts