标题： 探索微前端：电子商务中的案例应用 显示英文标题

标题： Exploring Micro Frontends: A Case Study Application in E-Commerce

摘要： 在微前端架构风格中，前端被划分为更小的组件，这些组件可以从一个简单的按钮到整个页面。 目标是提高可扩展性、弹性和团队独立性，尽管会增加复杂性和基础设施需求。 本文旨在了解在工业背景下采用微前端是否值得。 为此，我们基于学术和灰色文献对微前端的最新技术进行了调查。 然后，我们在一个已经使用微服务的手工艺品市场中实现了这种架构风格。 最后，我们通过半开放问卷对实现进行了评估，问卷对象是开发人员。 在研究的市场公司中，由于其主要系统（一个Java单体应用）与专用前端系统的紧密耦合，需要进行架构变更。 此外，还存在过时的技术和较差的开发人员体验。 为了解决这些问题，采用了微前端架构，以及API网关和前端后端模式，并使用了Svelte和Fastify等技术。 尽管微前端的采用是成功的，但并不严格必要以满足公司的需求。 根据混合问卷结果的分析，其他替代方案，如单体前端，也可以达到类似的效果。 在公司的背景下，采用微前端最方便的原因是单体应用的削弱和微服务的采用，这通过基础设施重用和团队间知识共享促进了实现。 显示英文摘要

摘要： 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.