Distributed deployments

The other extreme in terms of deployment scenarios is to create a fully distributed deployment system. Here, each micro frontend needs to come up with its own CI pipeline, which could leverage any kind of provider outside. Information regarding which micro frontends are available would be aggregated either by a central service or some federated approach, where individual micro frontend mirrors are known in a registry. This registry may be distributed, too. In practical scenarios, such a registry would be centralized.

A big advantage of distributed deployments lies in the independence of the individual micro frontends, whereby each team is fully responsible for their artifact. This statement is not only written on paper, but truly exists in the basic setup of the application itself. If a team is unable to set up a proper release pipeline, nothing will happen and their contribution will never be noticed.

As with central deployments, we can look into two...