Hybrid solutions

Quite often, the main reason for introducing micro frontends is the scalability in terms of development (dev) teams. Therefore, as outlined, going in the direction of distributed deployments seems natural and has the biggest scaling impact. Nevertheless, for one reason or another, there may be a collective of micro frontends that should be deployed—or at least developed—in a single repository. Now is the time to talk about a third way of doing deployments using micro frontends—namely, a hybrid solution.

Hybrid solutions try to leverage the advantages of both extremes: a central deployment solution and a distributed deployment system. As a result, challenges that come with hybrid solutions are usually a combination of challenges pertaining to both solutions.

Usually, going for a hybrid solution is motivated by the ability to have scheduled releases for a set of micro frontends. An alternative is to just trigger a release when any of the micro...