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

Central deployments

While having one large release is often considered a downside of monoliths, it also can be seen as a desired solution. After all, this is an easy way to ensure we have one unit that works together. In this solution, we can also control very well when the application updates. Finally, the ultimate advantage of using a central deployment for micro frontends is that we can join the micro frontends that are already upfront. This allows optimizations and enhancements that would be very hard to incorporate in a non-central pipeline.

It turns out there are two major ways of thinking about a central CI pipeline, outlined as follows:

  • Using a mono repository (monorepo)
  • Joining multiple repositories

While the former is easier to set up, the latter may be closer to what the majority of users are after. Let's have a look at both.

Using a monorepo

Monorepos have become quite popular, one reason being that they allow the mixing of different packages...