Entity Framework is a $100 Million Mistake ( We Use Dapper + Raw SQL)

Your database queries are costing you users.

I know because I watched 847 users abandon the fintech app that I was working on in one week. They’d click “View Portfolio” and just… leave. Gone. $50K in potential revenue vanished. (Client was just yelling, but you already know only I can fix it, so I was chill, but..

The Issue: Every single abandonment happened at the same spot — when our app took more than 8 seconds to load their portfolio data. Eight seconds of spinning loader. Eight seconds of wondering if the app was broken. Eight seconds are too long, man, and for the trader it can be a scary dream…

Well, I found that it’s been a long time since we've been using EF Core, and actually, I didn’t do that, but it was juniors who wrote code sometimes, and my coffee just didn’t allow me to look before merging it. Anyway, maybe he was thinking Microsoft’s “Supa ORM” would handle everything.

it was generating SQL queries so bloated and inefficient that our database server was choking on what should…