Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • The Art of Micro Frontends
  • Toc
  • feedback
The Art of Micro Frontends

The Art of Micro Frontends

By : Florian Rappl
4 (9)
close
The Art of Micro Frontends

The Art of Micro Frontends

4 (9)
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)
close
1
Section 1: The Hive - Introducing Frontend Modularization
6
Section 2: Dry Honey - Implementing Micro frontend Architectures
14
Section 3: Busy Bees - Scaling Organizations

Basics of the web approach

The web approach of implementing micro frontends works by referring to individual micro frontends via their URL. The basic principle is shown in the following diagram:

Figure 6.1 – Idea behind the web approach – different servers providing different parts of the application

In this pattern, teams are going for whole pages and are only governed by a centrally given design and business domain.

In practical applications, following the basic principle, this could mean that the origins change during the navigation. For instance, we could start at www.example.com, but then navigate to mf1.example.com.

More often, however, it means that the real web servers are hidden behind a kind of gateway as implemented in our previous sample. In this case, the origin would remain the same, but the paths may change, for example, navigating from / to /mf1.

Let's look right into the architecture of the web approach before doing...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete