What Is Vertical Slice Architecture? Here's How I Use It in Blazor 🖥️


Hey Reader,

After 15 years of building web apps, I just recently discovered Vertical Slice Architecture.

I know. I’m late to the party.

But wow, this approach really changed how I think about structuring Blazor projects. So I decided to show you a simple, real-world example of how to use Vertical Slice Architecture in a Blazor Server app.

🎥 Watch the full tutorial now:

video preview

In this new tutorial, you'll learn:
✅ How to structure your app with feature folders
✅ How to avoid overcomplicating things with too many layers
✅ How to use Entity Framework and SQL Server in a clean, straightforward way
✅ How to build and wire up a real edit form in Blazor
✅ Why Vertical Slice Architecture keeps things tidy and cohesive

I walk you through every step: from setting up the DB context to wiring up the Razor page. And yes, you’ll get all the source code to follow along.

Hope you enjoy this one. Let me know in the comments if you’d like a deeper dive into Vertical Slice Architecture. I’d love to make a part 2!

Take care,

Patrick

P.S. Yes, I left that typo in the code on purpose. Totally. 😉

P.P.S. Want to go deeper into real-world .NET and Blazor projects? Join me inside the .NET Web Academy. Check it out here.


.NET Web Academy

Become a .NET & Blazor expert with weekly tutorials featuring best practices and the latest improvements, right in your inbox.

Read more from .NET Web Academy

Hey friend, A developer I know built his whole career on one bet: that young developers would never want to touch old code. So the legacy systems quietly running real companies would always need someone, and he would be that someone. For twenty years it paid. Then AI arrived and went straight for the part he thought was safe. Because the hardest part of modernizing an old system was never the typing. It was the understanding. Reconstructing thirty projects and three contractors' worth of...

Hey friend, The other day I found a bug in StackBuddy, an app I built. Normally I'd open it, file a ticket for myself, and move on. Instead I turned to my AI and just said, "log a dev ticket for that." And it did. A real ticket in my own bug tracker. Title, description, priority, the whole thing. I never opened the actual app. The thing that makes that possible is called MCP, Model Context Protocol. Ignore the name for a second. Out of the box, an AI can only talk. It writes and explains, but...

Hey friend, I don't really write code by hand anymore. I describe what I want, and the AI builds it. For a while, that scared me. If I am not writing the code, does everything I spent years learning still matter? Does my stack matter at all? If you are a developer right now, I would bet you have felt some version of that too. Here is where I landed. It flipped the whole thing for me. The other day I was debugging a slow app, talking it through with the AI. Would WebAssembly help here? Is it...