For a decade now there has been a silent game changer coming to web application development. It's not common to have a fourth language added to the web development stack. With advent of .NET 8 it has been easier than ever before to take advange of WASM.
So consider this. Some web apps need rich interactive UIs. These are often called Single Page Applications or SPAs, but many web apps just need to generate plain HTML to handle requests as quickly as possible. Now many web apps use both of these techniques in different places. Maybe the public pages are displaying HTML and the logged-in area is a SPA.
Now in the past, this would have required two different technologies. For example in .NET to generate HTML we've got MVC and Razor pages with CSHTML files, whereas for interactive SPAs we've got Blazor WebAssembly or Blazor Server, so that's two different architectures.
But there's a growing trend within the industry to try and unify these into a single technology that can do both plain HTML and rich SPAs from one architecture. Now the point of this is you don't have to limit yourself to just one approach up front -- use whatever approach is relevant for each part of your app. You can mix and match even within a single page and easily switch if your requirements change.
Steve Sanderson
- Author
Patryk Nowak
Backend developer
- Comments
- Leave a Comment