Microservice backends enable autonomous teams, but a single monolithic frontend often leads to release train slowdowns and blockers.
Web architecture evolved from classic monoliths to separated frontends and microservice backends, making microfrontends the next logical step for scaling UI development.
A successful microfrontend architecture uses an app shell with independent modules and avoids strong coupling to prevent creating a distributed monolith with feature overlaps.
One approach is to use Blazor Razor Component Libraries (RCLs) as modules within a Blazor shell, keeping the entire solution within the C# ecosystem.
A hybrid approach uses a JavaScript-based app shell to lazy-load Blazor components, enabling framework flexibility and faster initial startup times.
The Piral framework facilitates a microfrontend architecture by using a feed service to dynamically load and compose independent modules, called pilets, into a cohesive application shell.
The discussion covers whether Blazor is a best practice, preferred lightweight frameworks like SolidJS, and strategies for migrating a monolith using the Strangler pattern.
59:03Florian Rappl
40:24Clemens Helm
20:15Menaka Baskerpillai
29:52Christian Giesswein
26:38Christian Giesswein
54:39Alexander Günsche
32:42Ryan Niño Dizon
40:05Florian Rappl
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
JO Media Software Solutions GmBh
Brunn am Gebirge, Austria
tarent solutions GmbH
tarent solutions GmbH