ASP.NET MVC in 2024: A Powerful Choice for Modern Web Development?
summary
Argues ASP.NET Core MVC remains a pragmatic choice in 2024 by trading surface area for predictability — MVC core docs ~200 pages vs Blazor ~1,400 — and by adopting vertical slices so a single feature file holds model, events, projections and Razor views, cutting the “change one property → edit seven files” problem. Demonstrates event sourcing with Marten on Postgres (inline projections for strong consistency), Wolverine for messaging, htmx for reactive server-rendered UI, multi-tenant patterns, and a working demo of the approach.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:31Journey to MVC
- 3:27Bootstrapping and MVC
- 5:42Developer flow state
- 7:00MVC framework features
- 12:41The monolith challenge
- 14:13MVC code structure
- 19:07Coupling and architecture
- 23:22Cohesion and locality
- 26:46The problem with clean architecture
- 30:36Vertical slice architecture
- 33:52Refined controller models
- 35:01Event sourcing patterns
- 38:39Implementing MartenDB
- 46:45HTMX for reactivity
- 48:18Live code demonstration
- 58:22Composition and wrap-up
related talks
01h 01mAdapting ASP.NET Core MVC to your needs
32mBuilding Secure ASP.NET Core MVC Applications
50mAdapting ASP.NET Core MVC to your needs
41mModern Full-Stack Web Development with ASP.NET Core & Blazor
01h 02mAdapting ASP.NET Core MVC to your needs
01h 01mAn Opinionated Approach to Using ASP.NET Core
01h 14mThe Future of Web Development with ASP.NET Core & Blazor in .NET 10
01h 00mIntroduction to ASP.NET Core Razor Pages
