Blazor architecture at scale

Who it is for

For teams and individuals who look after several Blazor applications or one large application and want to set cuts and boundaries deliberately.

Prerequisites

W8 Blazor in depth or equivalent practice, and K4 (architecture decisions, Azure).

Afterward, you can

• Find bounded contexts and record them as a context map
• Build a modular monolith with modules as projects and public contracts
• Run one solution with central build and package rules for several modules
• Enforce module boundaries with architecture tests in the build
• Version a design system as a NuGet package and find breaking changes with package validation
• Determine affected projects from a change and decide when micro frontends pay off

Contents

1. W11.1

   Cuts and modules

   bounded contexts, context map, modular monolith, public contracts

   6 h
2. W11.2

   Repository and boundaries

   one solution for several modules, central package management, architecture tests

   6 h
3. W11.3

   Libraries, CI, delivery

   design system as NuGet package, CI for affected projects, micro frontends

   10 h

About 22 hours in all (indicative).

Lessons

You see the text and video of every lesson here on the site after buying the course; the titles and goals are already shown. A self-study course: you work through the lessons in order and check your exercises yourself against the solutions.

You can read the first module (W11.1) for free, with text and video, without signing in: so you see how the course works before you buy.

The lessons stand under their modules, in the order of the course. Click a module to open or close its lessons.

Final project: the Kladde

Certifications

Microsoft offers no exam of its own for this.

Keep learning with Microsoft Learn

Microsoft's learning paths and documentation that go with this course.

• ASP.NET Core Razor class libraries
• NuGet package validation
• Central Package Management