Guidelines for adopting micro frontends

Abstract

Context: The size and structure of software development teams directly impact the design and construction of systems. According to Conway’s Law, the internal organization of teams influences the architecture of the systems developed, reflecting their communication flows. In the context of frontend architectures, approaches such as monolithic frontends, microservices, and microfrontends present different trade-offs in terms of performance, modularity, and scalability. While smaller teams tend to benefit from monolithic architectures due to their simplicity and agility, larger and distributed teams may adopt microfrontends to promote greater autonomy, scalability, and organizational alignment. This alignment between organizational structure and architecture is essential to ensure systems that are technically viable and aligned with the operational reality of teams. Problem: The integration between backend and frontend in microservices-based architectures is complex and requires solutions that balance modularity, specialization, and governance without compromising team cohesion. There is a lack of consolidated guidelines to support the adoption of microfrontends, both in the literature and in industrial practice. Objective: To propose a set of guidelines for the adoption of microfrontends in microservices-based environments, aiming to reduce risks, maximize benefits, and align architectural decisions with organizational structure. Method: The research was conducted based on the Design Science Research (DSR) methodology, focusing on the development and validation of an artifact. The following steps were carried out: (i) Systematic Literature Mapping, to characterize the state of the art; (ii) Multivocal Systematic Review, integrating academic and industrial evidence; (iii) Survey with industry professionals, to understand the state of practice; and (iv) empirical studies, including a controlled experiment and a case study, to evaluate performance and analyze the applicability of the proposed guidelines. Results: The results indicate that microfrontends are more suitable for organizations with higher maturity in DevOps practices, distributed teams, and systems with multiple business domains. Architectures based on monolithic applications were observed to provide better initial performance, whereas microfrontend-based architectures offer modularization mechanisms that may support both technical and organizational scalability, as evidenced by the literature and industry reports. The proposed guidelines encompass aspects of architecture, governance, integration, quality assurance, and team organization, and are grounded in evidence derived from the literature, industry practice, and experimental studies conducted in a controlled environment. Conclusion: The adoption of microfrontends should be context-driven and aligned with the organizational structure, as advocated by Conway’s Law. The proposed guidelines provide a structured set of recommendations grounded in academic, industrial, and experimental evidence, supporting architectural decision-making across different organizational contexts. The results obtained provide evidence regarding the technical aspects of the architecture and indicate the need for further studies in real-world environments to evaluate organizational and operational factors associated with microfrontend adoption.