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

Creating designs without designers

Ideally, screen designs are not done anymore. Instead, components are crafted directly by UX engineers, who do not need to hand over work for technical implementation. In such scenarios, the technical implementation of these components is already done by them.

The outcome of such setups is a pattern library that can be used by all teams. This library might be as low level as a set of CSS classes with HTML fragments and JavaScript snippets – sometimes even packaged up as Web Components – or provided already for specific frameworks. For instance, these can be shipped as a React component library.

One advantage of framework-specific libraries is that they can be used within that framework very easily, and they are usually more efficient than generic libraries that require additional embedding. The inefficiency for the latter does not come from generic JavaScript, but rather from not being able to use framework-specific optimizations...