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

Establishing a governance model

The whole purpose of governance is defining processes to simplify everything that is happening and that is necessary for the product. This starts at the initial required analysis stage and ends with maintenance efforts.

From a technical point of view, a governance model helps us to identify what processes can be left unautomated and which ones do need automation.

In general, there are multiple areas that can be covered, as follows:

  • Business analysis (such as roadmaps, timelines, and monetarization)
  • Requirement definitions (such as use cases, effort, and risks)
  • Software architecture (such as performance and security)
  • UX design (such as guidelines)
  • Implementation (such as code quality and feature implementation)
  • Testing (such as plans, coverage, and scores)
  • Documentation (such as documents)
  • Deployment (such as instructions)
  • Maintenance (such as troubleshooting, bugs, and feature requests)

While some...

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