We're starting a greenfield service and trying to decide whether to standardize on Dapper or EF Core. The team likes Dapper's speed and lack of abstraction, but I'm nervous about losing change tracking, migrations, and LINQ composability later on.

For a new ASP.NET Core API with moderate domain complexity — roughly 15 entities, some reporting endpoints, and a couple of CRUD screens — what would you actually pick today? I'd rather hear from folks who've lived through the maintenance pain of one or the other, not just benchmark numbers.