Is your frontend slowing down innovation and complicating team collaboration? Consider micro-frontends—a practical way to break development silos and accelerate feature delivery. In this updated second edition, software architects, tech leads, and software developers will learn how to design, build, and deploy independent micro-frontends that compose unique frontend systems.

Author Luca Mezzalira, principal serverless specialist solutions architect at AWS, shows you how micro-frontends enable agility within an organization, decentralize decision-making, and optimize for fast flow. This gives your organization technical flexibility and allows you to hire and retain a broad spectrum of talent. Micro-frontends also support distributed or colocated teams more efficiently. Start transforming your frontend strategy today with proven techniques for speed of delivery, autonomy, and scale.

• Accelerate delivery with four foundational pillars for micro-frontend success
• Apply actionable principles and best practices to empower your teams
• Navigate the benefits and pitfalls of micro-frontend architectures
• Integrate micro-frontends seamlessly with microservices and distributed systems
• Architect client-side and server-side micro-frontend solutions for maximum impact

Osoby które kupowały "Building Micro-Frontends. Distributed Systems for the Frontend. 2nd Edition", wybierały także:

• Jak zhakowa 125,00 zł, (10,00 zł -92%)
• Windows Media Center. Domowe centrum rozrywki 66,67 zł, (8,00 zł -88%)
• Ruby on Rails. Ćwiczenia 18,75 zł, (3,00 zł -84%)
• Efekt piaskownicy. Jak szefować żeby roboty nie zabrały ci roboty 59,50 zł, (11,90 zł -80%)
• Przywództwo w świecie VUCA. Jak być skutecznym liderem w niepewnym środowisku 58,64 zł, (12,90 zł -78%)

Spis treści

Building Micro-Frontends. Distributed Systems for the Frontend. 2nd Edition eBook -- spis treści

• Foreword for the 1st Edition
• Preface
  • Why I Wrote This Book
  • Who This Book Is For
  • How This Book Is Organized
  • Conventions Used in This Book
  • Using Code Examples
  • OReilly Online Learning
  • How to Contact Us
  • Acknowledgments
• 1. Micro-Frontend Principles
  • Monolith to Distributed Systems
  • Moving to Microservices
  • Introducing Micro-Frontends
  • Microservices Principles
    • Modeled Around Business Domains
    • Culture of Automation
    • Hidden Implementation Details
    • Decentralization
    • Independent Deployment
    • Isolated Failures
    • Highly Observable
  • Applying Principles to Micro-Frontends
    • Modeled Around Business Domains
    • Culture of Automation
    • Hidden Implementation Details
    • Decentralization
    • Independent Deployment
    • Isolated Failures
    • Highly Observable
  • Challenges Unique to Micro-Frontends
  • Micro-Frontends Are Not a Silver Bullet
  • Summary
• 2. Micro-Frontend Architectures and Challenges
  • Micro-Frontend Decision Framework
  • Defining Micro-Frontends
  • DDD with Micro-Frontends
  • How to Define a Bounded Context
  • Testing Your Micro-Frontend Boundaries
  • Micro-Frontend Composition
    • Client-Side Composition
    • Edge-Side Composition
    • Server-Side Composition
  • Routing Micro-Frontends
  • Micro-Frontend Communication
  • Micro-Frontends in Practice
    • Zalando
    • Formula 1
    • Dunelm
    • Netflix
    • PayPal
    • BMW
    • OpenTable
    • DAZN
  • Summary
• 3. Discovering Micro-Frontend Architectures
  • Application of the Micro-Frontend Decision Framework
    • Vertical Split
    • Horizontal Split
  • Architecture Analysis
  • Architecture and Trade-Offs
  • Vertical-Split Architectures
    • Application Shell
    • Challenges
      • Sharing state
      • Composing micro-frontends
      • Multi-framework approach
    • Architecture Evolution
    • Implementing a Design System
    • Developers Experience
    • Performance and Micro-Frontends
    • Available Frameworks
    • Architecture Characteristics
  • Horizontal-Split Architecture
    • Client Side
    • Challenges
      • Micro-frontend communication
      • Clashes with CSS class names and how to avoid them
      • Multi-framework approach
      • Authentication
    • Micro-Frontend Refactoring
    • Search Engine Optimization
    • Developer Experience
    • Team Communication and Best Practices for Maintaining Control of the Final Outcome
    • Use Cases
    • Available Frameworks
      • Module Federation
      • Performance
      • Composition
      • Shared code
    • Developer Experience
    • Use Cases
    • Architecture Characteristics
  • iframes
    • Best Practices and Drawbacks
    • Developer Experience
    • Use Cases
    • Architecture Characteristics
  • Web Components
    • Web Components Technologies
    • Dependency Management
    • Use Cases
    • Architecture Characteristics
  • Web Fragments
  • Server Side
    • Scalability and Response Time
    • Infrastructure Ownership
    • Composing Micro-Frontends
    • Micro-Frontend Communication
    • Available Frameworks
    • Use Cases
    • Architecture Characteristics
  • Modern Server-Side Rendering Frameworks
    • Use Cases
    • Architecture Characteristics
  • Edge Side
  • Summary
• 4. Client-Side Rendering Micro-Frontends
  • The Project
  • Module Federation 101
  • Technical Implementation
    • Project Structure
    • Application Shell
    • Home Micro-Frontend
    • Catalog Micro-Frontend
    • Account Management Micro-Frontend
  • Project Evolution
    • Embedding a Legacy Application
    • Developing the Check-Out Experience
    • Hosting a Client-Side Rendering Micro-Frontend Project
    • Caching
  • Summary
• 5. Server-Side Rendering Micro-Frontends
  • When to Use Server-Side Rendering
  • Scalability Challenges
  • Dividing Micro-Frontends
  • Composition Approaches
  • The Main Challenge
  • HTML Fragments
  • Splitting by URL
  • The Formula 1 Website is Powered by Micro-Frontends
  • Next.js Multi-Zones
  • Home Zone: The Entry Point of Your Web Application
  • How to Handle Shared Components
  • How to Manage Data
    • Vercel: A Glance into the Future
  • API Strategies
  • Dont Fear the Cache: Scaling SSR with Smart Caching Strategies
  • Types of Caches Every Developer Should Know
    • Content Delivery Networks
    • In-Memory Database Cache
    • Warm Cache
  • The BBC Architecture: Caching in Action
  • Performance: The Key Reason for Server-Side Rendering
  • Summary
• 6. Micro-Frontend Automation
  • Automation Principles
    • Keep the Feedback Loop Fast
    • Iterate Often
    • Empower Your Teams
    • Define Your Guardrails
    • Define Your Test Strategy
  • Developer Experience
    • Horizontal Versus Vertical Split
    • Frictionless Micro-Frontend Blueprints
    • Environments Strategies
  • Version Control
    • Monorepo
    • Polyrepo
    • A Possible Future for a Version Control System
  • Continuous Integration Strategies
  • Testing Micro-Frontends
    • End-to-End Testing
    • Vertical-Split End-to-End Testing Challenges
    • Horizontal-Split End-to-End Testing Challenges
    • Testing Technical Recommendations
  • Fitness Functions
  • Micro-Frontend-Specific Operations
  • Observability
  • Summary
• 7. Discover and Deploy Micro-Frontends
  • Blue-Green Deployment Versus Canary Releases
  • The Problem Space
  • Welcome to the Frontend Discovery Schema
  • The Benefits of This Pattern
  • Real-World Implementation
  • An Integration Example with Module Federation
  • Integrating the Discovery Pattern with Other Solutions
  • What about Feature Flags?
  • Availability in the Market
    • Summary
• 8. Automation Pipeline for Micro-Frontends: A Case Study
  • Setting the Scene
  • Version Control
  • Pipeline Initialization
  • Code-Quality Review
  • Build
  • Post-Build Review
  • Deployment
  • Automation Strategy Summary
  • Summary
• 9. Backend Patterns For Micro-Frontends
  • API Integration and Micro-Frontends
  • Working with a Service Dictionary
    • Implementing a Service Dictionary in a Vertical-Split Architecture
    • Implementing a Service Dictionary in a Horizontal-Split Architecture
  • Working with an API Gateway
    • One API Entry Point per Business Domain
    • Client-Side Composition with an API Gateway and a Service Dictionary
    • Server-Side Composition with an API Gateway
  • Working with the BFF Pattern
    • Client-Side Composition with a BFF and a Service Dictionary
    • Server-Side Composition with a BFF and a Service Dictionary
  • Using GraphQL with Micro-Frontends
    • The Schema Federation
    • Using GraphQL with Micro-Frontends and a Client-Side Composition
    • Using GraphQL with Micro-Frontends and a Server-Side Composition
  • Best Practices
    • Multiple Micro-Frontends Consuming the Same API
    • APIs Come First, Then Implementation
    • API Consistency
    • WebSocket and Micro-Frontends
    • The Right Approach for the Right Subdomain
  • Summary
• 10. Common Antipatterns in Micro-Frontend Implementations
  • Micro-Frontend or Component?
  • Sharing State Between Micro-Frontends
  • Micro-Frontend Anarchy
  • Anti-Corruption Layer to the Rescue
  • Unidirectional Sharing
  • Premature Abstraction
  • Summary
• 11. Migrating to Micro-Frontends
  • Why Go Iterative?
  • Which Problem(s) Am I Trying to Solve with Micro-Frontends?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • How Can I Get the Management On Board with This Migration?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • How Should I Actually Plan the Migration?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • How Do I Decide Which Modules or Features to Migrate First?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • How Do I Maintain User Experience and Consistency During Migration?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • How Do I Handle Shared Dependencies and Version Management Between Legacy and Micro-Frontend Code?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • How Do I Manage Cross-Cutting Concerns Like Auth, Routing, or State During Migration?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • Do I Need Microservices to Migrate to Micro-Frontends?
    • Best Practices and Patterns
    • Trade-Offs and Pitfalls
    • Checklist
    • A Quick Example
    • Personal Experience
  • Summary
• 12. From Monolith to Micro-Frontends: A Case Study
  • The Context
    • Technology Stack
    • Platform and Main User Flows
    • Technical Goals
  • Migration Strategy
    • Micro-Frontend Decision Framework Applied
  • Splitting the SPA into Multiple Subdomains
  • Technology Choice
  • Implementation Details
    • Application Shell Responsibilities
    • Application Initialization
    • Communication Bridge
    • Mounting and Unmounting Micro-Frontends
    • Sharing State
    • Global and Local Routing
    • Migration Strategy
    • Backend Integration
    • Integrating Authentication in Micro-Frontends
    • Dependency Management
    • Integrating a Design System
    • Sharing Components
    • Implementing Canary Releases
    • Localization
  • Summary
• 13. Introducing Micro-Frontends in Your Organization
  • Why Should We Use Micro-Frontends?
  • Data to the Rescue
  • Creating a Trade-Off Analysis
    • Business Requirements
    • Architecture Characteristics
    • Organization Capabilities
  • The Link Between Organizations and Software Architecture
  • How Do Committees Invent?
  • Features Versus Components Teams
  • Implementing Governance for Easing the Communication Flows
    • Requests for Comments
    • Architecture Decision Records
  • Techniques for Enhancing the Communication Flow
    • Working Backward
    • Community of Practice and Town Halls
    • Managing External Dependencies
  • A Decentralized Organization
  • Decentralization Implications with Micro-Frontends
    • High-Complexity Subdomain
    • High Initial-Effort Subdomain
    • Normal-Complexity Subdomain
    • Low-Complexity Subdomain
  • Summary
• 14. AI and Micro-Frontends: Augmenting, Not Replacing
  • Architecture Is Not Yet Automatable
  • Context Engineering to the Rescue
  • Feasible AI Use Cases Today
    • Testing
    • Automation
    • Debugging with AI
    • Diagram Generation
    • Keeping the README Alive
    • Prototyping
    • Project Scaffolding
    • Code Optimization
    • Bouncing Ideas and Discovering Alternatives with Agentic AI
    • Accessibility
    • Code Migration
    • Discovering Alternatives and Challenging Assumptions with AI
  • My Playbook to Work with AI
    • Step 1: Define What You Want to Achieve
      • Why it matters
      • How to approach it
      • Effective prompting
      • Pitfalls to avoid
      • Key takeaways
    • Step 2: Engineer the Context; Dont Just Prompt
      • Why it matters
      • How to approach it
      • Effective prompting
      • Strategy: Embed context in the codebase
      • Prompt refinement example
      • Key takeaways
    • Step 3: Reason Like You Normally Would as a Developer
      • Why it matters
      • How to approach it
      • Effective prompting
      • When to use this pattern
      • Example: AI as design reviewer
      • Pitfalls to avoid
      • Key takeaways
    • Step 4: Iterate in Small, Focused Steps
      • Why it matters
      • How to approach it
      • Effective prompting
      • Now, consider this follow-up prompt:
      • Why this works
      • Antipattern: The one prompt to rule them all
      • Key takeaways
    • Step 5: Review and Refactor the Output
      • Why it matters
      • How to approach it
      • Example scenario
      • Prompt pattern for review
      • Key takeaways
    • Step 6: Automate Through AI
      • Why it matters
      • How to approach it
      • Effective prompting
      • Key takeaways
  • Where Code Assistants and AI Fall Short
    • Understanding Code Change Operations
  • What the Future Holds for AI and Micro-Frontends
• Index