Context:

Micro-Frontends are increasing in popularity, being adopted by several large companies, such as DAZN, Ikea, Starbucks and may others. Micro-Frontends enable splitting of monolithic frontends into independent and smaller micro applications. However, many companies are still hesitant to adopt Micro-Frontends, due to the lack of knowledge concerning their benefits. Additionally, provided online documentation is often times perplexed and contradictory.

Objective:

The goal of this work is to map the existing knowledge on Micro-Frontends, by understanding the motivations of companies when adopting such applications as well as possible benefits and issues.

Method:

For this purpose, we surveyed the academic and grey literature by means of the Multivocal Literature Review process, analysing 173 sources, of which 43 reported motivations, benefits and issues.

Results:

The results show that existing architectural options to build web applications are cumbersome if the application and development team grows, and if multiple teams need to develop the same frontend application. In such cases, companies adopted Micro-Frontends to increase team independence and to reduce the overall complexity of the frontend. The application of the Micro-Frontend, confirmed the expected benefits, and Micro-Frontends resulted to provide the same benefits as microservices on the back end side, combining the development team into a fully cross-functional development team that can scale processes when needed. However, Micro-Frontends also showed some issues, such as the increased payload size of the application, increased code duplication and coupling between teams, and monitoring complexity.

Conclusions:

Micro-Frontends allow companies to scale development according to business needs in the same way microservices do with the back end side. In addition, Micro-Frontends have a lot of overhead and require careful planning if an advantage is achieved by using Micro-Frontends. Further research is needed to carefully investigate this new hype, by helping practitioners to understand how to use Micro-Frontends as well as understand in which contexts they are the most beneficial.

中文翻译：

---

采用微前端的动机，好处和问题：多声文学评论

语境：

Micro-Frontends越来越受欢迎，已被DAZN，宜家，星巴克等多家大公司采用。Micro-Frontends可以将单片前端拆分为独立的较小的微型应用程序。但是，由于缺乏有关其优势的知识，许多公司仍不愿采用Micro-Frontends。此外，提供的在线文档通常是困惑和矛盾的。

客观的：

这项工作的目的是通过了解公司采用此类应用程序的动机以及可能的收益和问题，来映射有关微型前端的现有知识。

方法：

为此，我们通过“多声文学评论”过程对学术和灰色文学进行了调查，分析了173种来源，其中43种报告了动机，收益和问题。

结果：

结果表明，如果应用程序和开发团队不断壮大，并且如果多个团队需要开发同一个前端应用程序，则用于构建Web应用程序的现有体系结构选项将很繁琐。在这种情况下，公司采用Micro-Frontends来增加团队独立性并降低前端的整体复杂性。Micro-Frontend的应用证实了预期的好处，而Micro-Frontends则提供了与后端微服务相同的好处，将开发团队组合成一个完全跨职能的开发团队，可以在需要时扩展流程。但是，Micro-Frontends还显示了一些问题，例如，应用程序的有效负载大小增加，团队之间的代码重复和耦合增加以及监视复杂性。

结论：

Micro-Frontends允许公司根据业务需求扩展开发规模，就像微服务在后端侧所做的一样。此外，如果使用Micro-Frontends获得优势，则Micro-Frontends会产生大量开销，并且需要仔细计划。需要进一步的研究来仔细研究这种新的炒作，方法是帮助从业人员了解如何使用微前端，以及了解它们在哪种情况下最有用。