Exploring Micro Frontends: A Case Study Application in E-Commerce
🤖 AI Summary
This paper addresses critical challenges in e-commerce frontends—tight coupling, outdated technologies, and poor developer experience—by empirically investigating the applicability boundaries of micro-frontend architecture. Method: Using a handcraft e-commerce platform as a case study, we incrementally decompose the monolith via an API gateway and Backend-for-Frontend (BFF) pattern, then implement Svelte-based micro-frontends atop an existing microservices infrastructure to achieve frontend-backend decoupling and team-autonomous delivery. Contributions: First, we systematically validate—within a real-world e-commerce setting—the necessity and inherent limitations of micro-frontends. Second, we demonstrate that leveraging an established microservice ecosystem significantly lowers adoption barriers. Third, we empirically show that micro-frontends are not universally superior: a well-architected monolithic frontend remains viable for equivalent functional goals, underscoring that architectural decisions must align closely with organizational capabilities and evolutionary maturity. Survey-based evaluation confirms measurable improvements but reinforces the principle of “context-sensitive” architecture selection.
Application Category
📝 Abstract
In the micro frontends architectural style, the frontend is divided into smaller components, which can range from a simple button to an entire page. The goal is to improve scalability, resilience, and team independence, albeit at the cost of increased complexity and infrastructure demands. This paper seeks to understand when it is worth adopting micro frontends, particularly in the context of industry. To achieve this, we conducted an investigation into the state of the art of micro frontends, based on both academic and gray literature. We then implemented this architectural style in a marketplace for handcrafted products, which already used microservices. Finally, we evaluated the implementation through a semi-open questionnaire with the developers. At the studied marketplace company, the need for architectural change arose due to the tight coupling between their main system (a Java monolith) and a dedicated frontend system. Additionally, there were deprecated technologies and poor developer experience. To address these issues, the micro frontends architecture was adopted, along with the API Gateway and Backend for Frontend patterns, and technologies such as Svelte and Fastify. Although the adoption of Micro Frontends was successful, it was not strictly necessary to meet the company's needs. According to the analysis of the mixed questionnaire responses, other alternatives, such as a monolithic frontend, could have achieved comparable results. What made adopting micro frontends the most convenient choice in the company's context was the monolith strangulation and microservices adoption, which facilitated implementation through infrastructure reuse and knowledge sharing between teams.
Problem
Research questions and friction points this paper is trying to address.
Evaluates when to adopt micro frontends in e-commerce systems
Assesses scalability and team independence trade-offs in frontend architecture
Compares micro frontends with monolithic alternatives for legacy systems
Innovation
Methods, ideas, or system contributions that make the work stand out.
Micro frontends split frontend into smaller components
Used API Gateway and Backend for Frontend patterns
Implemented with Svelte and Fastify technologies
🔎 Similar Papers
No similar papers found.
