Microfrontends in Angular with Mauricio Arce Torrez

Summary of episode #69 of the Angularidades podcast

Listen to the entire conversation in Spanish with Mauricio Arce Torrez on Spotify, YouTube, and other podcast platforms.

[embed]Episode #69 on YouTube

This episode of Angularidades welcomes Mauricio Arce Torrez, Technical Lead, Google Developer Expert in Angular, and creator of the YouTube channel combimauri. He is originally from Cochabamba, Bolivia and now based in Madrid.

[embed]combimauri ¡Hola a todos! Soy Mauricio Arce Torrez. 👋 Soy Ingeniero de Software y Google Developer Expert en Angular, viviendo y…www.youtube.com

In this conversation, Mauricio shares his experience and insights into the architecture of microfrontends in Angular: when to use them, their benefits, trade-offs, and how teams can successfully adopt them.

Key Points Discussed

What are microfrontends and why Angular does not natively support them

Mauricio explains how microfrontends extend the idea of microservices into the frontend. He highlights that the Angular framework optimizes for build-time improvements rather than runtime orchestration, leaving microfrontend architecture support to third-party tools.

When to consider microfrontends

Instead of application size, the key factors are complexity of domains, independence of features, and organizational structure. Microfrontends are valuable when teams require independent deployments, strong vertical boundaries, and autonomy across modules.

Tools and approaches

Mauricio discusses solutions like single-spa, Module Federation, Native Federation, iframes, and Web Components, explaining trade-offs and migration challenges between Module Federation and Native Federation.

Communication and design consistency

He outlines strategies for inter-microfrontend communication (shared services, custom events, routing, API calls) and stresses the importance of a shared design system, tokens, and component libraries to preserve consistent UX.

Challenges and anti-patterns

Key challenges include bundle size growth, version conflicts, and UI fragmentation. Alejandro and Mauricio warns against mixing multiple frameworks unnecessarily and against nesting microfrontends too deeply.

Practical advice

Mauricio encourages developers to experiment without fear, suggesting starting small with simple demos to understand the architecture. Alejandro adds another perspective: developers should not be deceived by the prefix "micro." Just like microservices, microfrontends are not necessarily tiny fragments. They should represent coherent verticals with real business logic, not every small component. Misinterpreting the concept can lead to inefficient and fragmented architectures.

At the end of the conversation, Mauricio and Alejandro reinforce that microfrontends are not always necessary, but when applied in the right contexts they can be a powerful architectural choice.

Stay tuned! Follow us on LinkedIn to check what’s next in future episodes.

Screenshot of episode #69