> Markdown version of [/videos/1012-micro-frontends-discovery](https://www.wearedevelopers.com/videos/1012-micro-frontends-discovery). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Micro-Frontends Discovery

Tired of nerve-wracking big bang deployments? Adapt backend service discovery to your frontend network layer. Unlock canary releases and confidently deploy dozens of times per day.

- **Speakers:** [Luca Mezzalira](https://www.wearedevelopers.com/@luca-mezzalira)
- **Event:** World Congress 2024
- **Published:** August 20, 2024
- **Duration:** 24:50
- **URL:** https://www.wearedevelopers.com/videos/1012-micro-frontends-discovery

## Summary

In monolith applications, deploying code is relatively straightforward, but moving to distributed micro-frontends introduces complex challenges around multi-environment strategies, component discoverability, and deployment robustness. Teams frequently rely on static configurations or manual import maps, which struggle to scale across environments and often result in nerve-wracking "big bang" deployments. By adapting the backend service discovery pattern to the frontend network layer, teams can decouple their architecture. When an application shell dynamically queries a service registry via an agnostic JSON schema rather than relying on hardcoded endpoints, it fundamentally changes how micro-frontends are loaded and managed.

This network-level decoupling naturally unlocks advanced release methodologies typically reserved for backend microservices, such as blue-green deployments and canary releases. Implementing an open-source, serverless discovery service simplifies integrating these deployment safeguards with existing CI/CD pipelines. This structure allows engineering teams to fractionally route live traffic, target specific regions or browsers, and safely test in production. Consequently, shifting from an all-or-nothing release strategy to a granular, dial-up process radically de-risks the pipeline and significantly reduces blast radiuses during errors.

Ultimately, a framework-agnostic approach requires no specific plugins for tools like Module Federation or single-spa, ensuring broad compatibility while minimizing performance overhead. By providing dynamic fallback routes and native support for continuous delivery patterns, organizations can culturally transform their engineering behavior. Eliminating the constant fear of catastrophic rollbacks fosters the confidence needed to deploy dozens of times per day and fluidly roll forward when addressing live issues.

**Keywords:** micro-frontends, service discovery pattern, blue-green deployment, canary release, module federation, single-spa, application shell, multi-environment strategy, open components, json schema, distributed frontend systems, deployment safeguards, traffic routing logic, serverless infrastructure, import maps

## Chapters

1. **Demonstrating the challenges of live production deployment and rollbacks** (00:02) — A live demonstration highlights the common friction points and risks when deploying new monolithic front-end application code.
1. **Transitioning monolithic page structures to distributed front-end architectures** (02:05) — Distributed micro-frontends require opinionated multi-environment strategies and robust component discovery to handle autonomous team deployments safely.
1. **Applying the service discovery pattern to micro-frontend architectures** (04:18) — Decoupling the application shell from explicitly defined environments using a registry enables highly dependable and resilient network-level routing.
1. **Applying blue-green and canary deployment strategies to front-end routing** (06:47) — Adopting modern micro-service deployment techniques enables developers to confidently target partial traffic logic during live feature rollouts.
1. **Creating a standardized JSON schema for framework-agnostic discoverability** (08:10) — A community-driven JSON structure allows modular orchestration of remote entries, multiple versions, and fallback payloads inside the host application.
1. **Evaluating the benefits and pitfalls of schema-based dynamic configurations** (13:15) — Serving configuration data at runtime minimizes front-end overhead but requires static fallback mechanisms to ensure high availability.
1. **Designing a serverless backend architecture to automate service discovery** (16:13) — An open-source state machine dynamically calculates version traffic increments and serves deployment manifests via an API gateway.
1. **Building organizational confidence through safe and incremental deployment strategies** (22:03) — Granular rollout capabilities build developer confidence to adopt rapid release iterations and replace fearful rollback mindsets with proactive roll-forward practices.

## Related Moments

- [Evolving architectures from backend microservices to micro frontends](https://www.wearedevelopers.com/videos/130-front-end-micro-apps) (from "Front-End Micro Apps")
- [Primary benefits of micro-frontend architectures](https://www.wearedevelopers.com/videos/299-micro-frontends-anti-patterns) (from "Micro-frontends anti-patterns")
- [Combining micro frontends and the modular monolith pattern](https://www.wearedevelopers.com/videos/492-stairway-to-heaven-scaling-frontends-the-right-way) (from "Stairway to Heaven - Scaling Frontends the Right Way")
- [Introduction to micro frontend architecture](https://www.wearedevelopers.com/videos/318-destructuring-frontend-monoliths-with-microfrontends) (from "Destructuring Frontend monoliths with MicroFrontends")
- [Understanding the engineering benefits of micro-frontend architectures](https://www.wearedevelopers.com/videos/420-micro-frontends-anti-patterns) (from "Micro-frontends anti-patterns")
- [Recapping frontend scaling patterns and distributed UI techniques](https://www.wearedevelopers.com/videos/236-microfrontends-at-scale) (from "Microfrontends at Scale")

## Related Articles

- [Dev Digest 138 - Are you secure about this?](https://www.wearedevelopers.com/magazine/486-dev-digest-138-are-you-secure-about-this)
- [Why You Shouldn’t Build a Microservice Architecture](https://www.wearedevelopers.com/magazine/118-why-you-shouldn-t-build-a-microservice-architecture)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [Dev Digest 139 - Soft and hard queries](https://www.wearedevelopers.com/magazine/487-dev-digest-139-soft-and-hard-queries)

## Related Jobs

- [Staff Frontend Engineer](https://www.wearedevelopers.com/jobs/48313-staff-frontend-engineer) at **SMG Swiss Marketplace Group**
- [Staff Frontend Engineer (Expert+/Lead equivalent) - Hybrid working model, 100%, Ho Chi Minh City](https://www.wearedevelopers.com/jobs/48314-staff-frontend-engineer-expert-lead-equivalent-hybrid-working-model-100-ho-chi-minh-city) at **SMG Swiss Marketplace Group**
- [Junior Frontend Engineer](https://www.wearedevelopers.com/jobs/ext/1532351-junior-frontend-engineer) at **Almedia**
- [Mid/Senior Full-Stack Engineer (Web-first)](https://www.wearedevelopers.com/jobs/ext/1210833-mid-senior-full-stack-engineer-web-first) at **SMG Swiss Marketplace Group**
- [Cloud Foundations Team](https://www.wearedevelopers.com/jobs/ext/1483289-cloud-foundations-team) at **GitHub**
- [Agile Full Stack Engineer](https://www.wearedevelopers.com/jobs/48325-agile-full-stack-engineer) at **synava GmbH**