Chapter 3. Discovering Micro-Frontend Architectures
In the previous chapter, we learned about the decision framework—the foundation of any micro-frontend architecture. In this chapter, we will review the different architecture choices, applying what we have learned so far.
Application of the Micro-Frontend Decision Framework
The decision framework helps you to choose the right approach for your micro-frontend project based on its characteristics, as shown in Figure 3-1.
Figure 3-1. Micro-frontend decision framework determining the best architecture for a project
Your first decision will be between a horizontal and vertical split.
Vertical Split
A vertical split offers fewer choices and less complexity because it is likely well known to frontend developers who are used to writing single-page applications (SPAs).
You’ll find a vertical split helpful when your project requires a consistent user interface evolution and a fluid user experience across multiple views. That’s because a vertical split provides the closest developer experience to an SPA, enabling developers to apply familiar tools, best practices, and patterns when building a micro-frontend.
In a vertical-split approach, the relation between a micro-frontend and the application shell is always one-to-one; therefore, the application shell loads only one micro-frontend at a time.
You’ll also want to use client-side routing ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access