Book Image

The Art of Micro Frontends

By : Florian Rappl
Book Image

The Art of Micro Frontends

By: Florian Rappl

Overview of this book

Micro frontend is a web architecture for frontend development borrowed from the idea of microservices in software development, where each module of the frontend is developed and shipped in isolation to avoid complexity and a single point of failure for your frontend. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will take you through the patterns available for implementing a micro frontend solution. You’ll learn about micro frontends in general, the different architecture styles and their areas of use, how to prepare teams for the change to micro frontends, as well as how to adjust the UI design for scalability. Starting with the simplest variants of micro frontend architectures, the book progresses from static approaches to fully dynamic solutions that allow maximum scalability with faster release cycles. In the concluding chapters, you'll reinforce the knowledge you’ve gained by working on different case studies relating to micro frontends. By the end of this book, you'll be able to decide if and how micro frontends should be implemented to achieve scalability for your user interface (UI).
Table of Contents (21 chapters)
1
Section 1: The Hive - Introducing Frontend Modularization
6
Section 2: Dry Honey - Implementing Micro frontend Architectures
14
Section 3: Busy Bees - Scaling Organizations

Summary

In this chapter, you learned that conceptual alignment and organization are as crucial—if not more crucial—as the actual implementation of micro frontends. After all, the domain decomposition gives us the boundaries that are needed to organize teams, define APIs, and assign functionality to the different modules.

You learned some basic vocabulary from DDD and how a context map can help you to organize the different bounded contexts that have been derived from the identified subdomains. You've seen that DDD tries to put everything into smaller chunks using a tech-agnostic language, such that the implementation can be chosen independently.

You also learned that a clear SoC and strict architectural boundaries lead to more fine-grained modules with clear team responsibilities.

In the next chapter, we will get an overview of the available types of micro frontends, which types exist, and when they should be used.