Posts

Mixed Render Modes in Blazor: Stop Making Your Entire App Interactive

-
Image
  For years, the first choice you made in a Blazor project set the course for your entire architecture: "This is a Blazor Server app." "This is a Blazor WebAssembly app." That single binary choice locked down your deployment, your hosting costs, and your state management across every single screen. Modern Blazor Web Apps removed that constraint. Within a single application, you can mix static server-rendered pages, server-side interactive circuits, and client-side WebAssembly components. You can even host multiple rendering models on the exact same page. Yet, many teams still build apps as if it's 2020. They slap @rendermode InteractiveServer onto their root Routes component and call it a day. Making everything interactive by default introduces unnecessary complexity, persistent SignalR circuit overhead, bloated WASM downloads, and elevated server memory usage. A far more practical strategy is to start static by default, then drop in interactivity only where t...
Post a Comment
Read more

Blazor Server can feel almost magical.

-
Image
  You write a Razor component: Razor CSHTML <button @onclick="IncrementCount"> Count: @count </button> @code { private int count; private void IncrementCount() { count++; } } The user clicks the button. C# runs on the server. The browser updates. No APIs, no controllers, no custom JavaScript handlers, no explicit fetch calls. It just works. Under the hood, though, there's a specific piece of architecture holding this together: the Blazor circuit . If you're building server-side Blazor apps without a firm grasp on how circuits function, you're flying blind on state management, memory overhead, connection drops, and scaling strategy. Here is what is actually happening under the hood—and how to design around it. What Is a Blazor Circuit? At its core, a circuit is the server-side memory state allocated for a single interactive user session. While your HTML is rendered in the user's browser, the component instances, even...
Post a Comment
Read more