Building Micro-Frontends, 2nd Edition

Chapter 8. Automation Pipeline for Micro-Frontends: A Case Study

Now that we’ve discussed the theory of a micro-frontend automation pipeline, let’s review a fictional use case example, including the different steps that should be taken into consideration based on the topics we have covered. Keep in mind that not all the steps or the configuration described in this example have to be present in every automation strategy, because companies and projects are different.

Setting the Scene

ACME Inc., a video-streaming service, empowers its developers and trusts them to know better than anyone else in the organization which tools they should use for building the micro-frontends needed for the project. Every team is responsible for setting up its micro-frontend build, so the developers are encouraged to choose the tools that meet the technical requirements of their micro-frontends and to operate within the boundaries, or guardrails, defined by the company.

The company uses a custom cloud automation pipeline with Docker containers, with the cloud team providing the tools required to run these pipelines. This Docker-based approach ensures environmental parity across local development, continuous integration (CI), and production—an essential factor for maintaining consistency and reliability across distributed micro-frontends.

The project is structured using micro-frontends with a vertical-split architecture, where each micro-frontend is technically represented by an HTML page, a JavaScript ...