Building Micro-Frontends, 2nd Edition

Chapter 7. Discover and Deploy Micro-Frontends

The last stage of any automation strategy is the delivery of the artifacts created during the build phase. Whether we decide to deploy our code via continuous deployment, a shell script running on premises, in a cloud provider, or via a user interface, understanding how we can deploy micro-frontends independently from each other is fundamental.

By their nature, micro-frontends must be independent. The moment we have to coordinate a deployment with multiple micro-frontends, we should question the decisions that we made in identifying their boundaries. Coupling risks can jeopardize the entire effort of embracing this architecture, generating more issues than value for the company. With microarchitectures, we deploy only a small portion of code without impacting the entire codebase. As with micro-frontends and microservices, we may decide to move forward to avoid the possibility of breaking the application and, therefore, the user experience. We’ll present the new version of a micro-frontend to a smaller group of users instead of doing a big-bang release to all our users. For this scope, the microservices world uses techniques like blue-green deployment and canary releases, where a portion of the traffic is redirected to a new microservice. Adapting these key techniques for any micro-frontend deployment strategy is worth considering. 

Blue-Green Deployment Versus Canary Releases

Blue-green deployment starts with the assumption that ...