ADR-0007: Blazor micro-frontend (MFE) for the Studio¶
- Status: Accepted
- Date: 2026-01-01
- Deciders: Frontend Architect, UX Lead
- Tags: frontend, studio, ui
Context¶
The Factory Studio is the primary human surface, composed of many independently evolving modules (dashboards, orchestration manager, knowledge base, observability, governance). It needs independent module delivery, a shared design system, and tight integration with the .NET backend and identity model.
Decision¶
Build the Studio as a Blazor micro-frontend (MFE) architecture: each Studio module is an independently developable/deployable micro-frontend composed into the shell, sharing a common design system and auth context. Mobile surfaces use MAUI where native apps are required.
Consequences¶
Positive¶
- One language/stack (.NET) across backend and frontend; shared models and auth.
- Independent module delivery and team ownership; consistent design system.
Negative / trade-offs¶
- MFE composition and versioning complexity; shared shell contract to maintain.
Neutral¶
- BFF APIs mediate between Studio modules and platform services.
Alternatives considered¶
| Alternative | Why not chosen |
|---|---|
| SPA framework (React/Angular) | Splits the stack from the .NET backend; duplicates models and tooling. |
| Single monolithic Blazor app | Couples module release cadences; harder to scale teams. |