Building Micro-Frontends (for True Epub) (Luca Mezzalira)（Z-Library）

# Building Micro-Frontends (Second Edition) — Reading Guide ## 【One-Line Pitch】 A practical, architecture-first guide for software architects, tech leads, and senior developers who want to break monolithic frontends into independently deployable, team-owned micro-frontends — covering everything from design patterns to CI/CD and real-world migration strategies. ## 【Book Arc】 - **Opening (~0%–10%)**: Defines micro-frontends as the frontend answer to microservices, introduces the core challenges (shared state, routing, performance, UX consistency), and establishes why distributed frontend systems demand different thinking than monoliths. - **Early (~10%–23%)**: Explores the two fundamental split strategies — vertical (page/domain-based) and horizontal (component-based) — with architecture characteristics, trade-offs, and composition technologies like Module Federation and Web Components. - **Early (~23%–32%)**: Dives into implementation details: authentication patterns, refactoring approaches, server-side rendering strategies, and concrete Module Federation configurations for hosts and remotes. - **Middle (~32%–48%)**: Moves to operational concerns — CI/CD pipelines, DevOps culture, deployment strategies, feature flags versus service discovery, and edge computing considerations. - **Late (~48%–end)**: Covers antipatterns to avoid, migration methodologies (asking the right questions, setting priorities), and a full case study of ACME Inc.'s journey from monolith to micro-frontends. ## 【Key Takeaways】 - **Micro-frontends solve organizational scaling, not just technical problems** (Opening): The architecture exists to let multiple teams ship independently — if you don't have team autonomy as a goal, the complexity may not be worth it. - **Shared state across micro-frontends is an antipattern** (Early): Using a global state manager creates coupling between teams, defeating the purpose of distributed systems. Instead, use events, callbacks, or service discovery for communication. - **Vertical and horizontal splits have different trade-offs** (Early): Vertical splits (page/domain-based) score higher on deployability (5/5) but lower on modularity (3/5); horizontal splits enable finer-grained composition but demand more sophisticated communication strategies. - **Module Federation is the current sweet spot for runtime composition** (Early): It abstracts away much of the complexity of loading shared code and micro-frontends at runtime, works within the bundler ecosystem, and supports both split strategies. - **Web Components provide encapsulation but require discipline** (Early): Custom elements and Shadow DOM give style and DOM isolation, but you must avoid leaking domain logic through the wrapper's customizable properties. - **CI/CD is where micro-frontends live or die** (Middle): With many independent artifacts, automation speed and reliability depend on fast feedback loops, team ownership of pipelines, and clear guardrails set by leadership. - **Feature flags and service discovery serve different purposes** (Middle): Reserve feature flags for runtime configuration within a micro-frontend; use service discovery for broader deployment strategies like rolling out a new check-out flow across multiple micro-frontends. - **Migrations succeed through questions, not just code** (Late): The book emphasizes identifying priorities and asking the right organizational questions before tackling the technical work of moving from a monolith. ## 【Reading Tips】 - **Skim the architecture characteristics tables** (Early chapters): The 5-point ratings for deployability, modularity, testability, and performance give you a quick comparison framework — revisit them when choosing between vertical and horizontal splits. - **Deep-read the Module Federation configuration examples** (Early ~29%): The code snippets showing host/remote setups are the most actionable material — study them carefully even if you skip other code. - **Pay attention to the F1 case study** (Middle ~32%): The real-world metrics (34% increase in subscriptions, 26% cost reduction) ground the theory in measurable outcomes — useful for justifying micro-frontends to stakeholders. - **Don't skip the antipatterns chapter** (Late): The author's five years of consulting experience surfaces mistakes you'll likely encounter — reading this before designing your architecture saves costly rework. - **If you're new to distributed frontends, read Chapters 1–3 first** (Opening–Early): The foundational concepts of splits, composition, and communication patterns are essential context before jumping to implementation or migration chapters. ## 【Coverage Limits】 This guide synthesizes the first ~48% of the book in depth (through CI/CD and deployment strategies). The later chapters on antipatterns, migration methodology, and the ACME Inc. case study are summarized from the table of contents but not detailed from excerpt content. ##