Building Micro-Frontends, 2nd Edition

Chapter 2. Micro-Frontend Architectures and Challenges

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the second chapter of the final book. Please note that the GitHub repo will be made active later on.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the author at [e-mail].

A micro-frontend represents a business subdomain that is autonomous, independently deliverable, with same or different technology, with low degree of coupling and owned by a single team. We can summarize the key takeaways in this description with the following characteristics:

• Business domain representation

• Autonomous codebase

• Independent deployment

• Low coupling

• Optimized for fast-flow

• Single-team ownership

Micro-frontends offer many opportunities. Choosing the right one depends on the project requirements, the organization structure, and the developer’s experience.

In these architectures, we face some specific challenges to success bound by similar questions, such as how we want to communicate between micro-frontends, how we want to route the user from one view to another, and, most importantly, how we identify the size of a micro-frontend.