Minimal APIs, CQRS, DDD… Or Just Use Controllers?
You've probably seen this meme floating around — it's funny because, well... there’s some truth to it. On one end, you’ve got people keeping it simple with MVC Controllers. On the other end? Also MVC Controllers. But in the middle, we’re neck-deep in abstractions: CQRS, MediatR, DDD, FastEndpoints, Aspire... the list goes on. 🔗 Kurrent (formely EventStoreDB) https://kurrent.io 🔔 Subscribe: / @codeopinion 💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon / codeopinion ✔️ Join via YouTube / @codeopinion 📝 Blog: https://codeopinion.com 👋 Twitter: / codeopinion ✨ LinkedIn: / dcomartin 📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo... 0:00 Intro 1:14 Starting Example 2:51 Remove Repository 6:06 Remove MediatR 8:39 What's the problem?
Should You Use Controllers or Minimal APIs in .NET?
Double Dispatch in DDD: When Injecting Dependencies Makes Sense
5 Mistakes That Make Your Code Unmaintainable
The Modular Monolith: Scale Without Microservices
You Don't Know OOP (But You Think You Do) !
Why Event-Driven Architecture Feels Broken
Why Domain-Driven Design Feels So Complicated (And How to Fix It)
Eventual Consistency: Good, Bad, and a HUGE Mistake
Fix Your Controllers By Refactoring To Minimal APIs
Forget Controllers and Minimal APIs in .NET!
Stop Copying the Customer Table in Every Service
Roy Fielding Says: Don’t Version APIs. Here’s Why.
167. Should I Create A Minimal API Or Full API?
10 Years of Software Architecture: Best And Worst Decisions
Stop using Event-Driven Architecture for your CRUD apps
I Removed MediatR – Building Your Own CQRS Handlers in .NET
STOP using Minimal APIs for Large Projects!
Do I Need MediatR in Vertical Slice Architecture?
Does MediatR Even Make Sense Anymore in .NET?
