Micro-Frontends Discovery

Stop hardcoding micro-frontend configurations. This talk introduces a service discovery pattern that enables canary releases and eliminates risky, 'big bang' deployments.

#1about 3 minutes

The challenge of deploying distributed frontends

Traditional deployment strategies for monoliths fail for micro-frontends, which require a solution for dynamic discovery across multiple environments.

#2about 2 minutes

Applying the service discovery pattern to frontends

The service discovery pattern, borrowed from backend microservices, decouples the application shell from specific micro-frontend versions by using a central registry.

#3about 1 minute

Enabling advanced deployment strategies for safety

Using a discovery service at the network level allows for safe deployment strategies like blue-green and canary releases to de-risk production changes.

#4about 1 minute

Creating a standard for micro-frontend metadata

A community collaboration resulted in a standard, framework-agnostic JSON schema to define and discover micro-frontends consistently.

#5about 2 minutes

A deep dive into the micro-frontend JSON schema

The schema includes essential fields like URL, version, and integrity, plus a flexible `extras` object for framework-specific needs like preloading chunks.

#6about 2 minutes

Implementing canary releases with the schema

The schema's array structure supports multiple versions, and an optional deployment object allows for defining precise traffic-splitting rules for canary releases.

#7about 3 minutes

Benefits and pitfalls of the schema-based approach

This approach is extensible and framework-agnostic but requires the configuration to be loaded first and is best implemented on the backend for security.

#8about 2 minutes

An open source serverless implementation on AWS

The MFS Discovery Service is an open-source, serverless tool that provides a ready-to-use implementation of the discovery and deployment patterns on AWS.

#9about 4 minutes

The architecture of the MFS discovery service

The service uses a backend API for CI/CD pipelines to manage deployments and a consumer API for the application shell to fetch the current configuration.

#10about 3 minutes