You're reading from The Art of Micro Frontends Build websites using compositional UIs that grow naturally as your application scales

Product type Paperback

Published in Jun 2021

Publisher Packt

ISBN-13 9781800563568

Length 310 pages

Edition 1st Edition

Languages

JavaScript

Tools

React

Concepts

Front End Web Development

Author (1):

Florian Rappl

View More author details

Table of Contents (21) Chapters

Preface

1. Section 1: The Hive - Introducing Frontend Modularization

2. Chapter 1: Why Micro frontends? FREE CHAPTER

3. Chapter 2: Common Challenges and Pitfalls

4. Chapter 3: Deployment Scenarios

5. Chapter 4: Domain Decomposition

6. Section 2: Dry Honey - Implementing Micro frontend Architectures

7. Chapter 5: Types of Micro Frontend Architectures

8. Chapter 6: The Web Approach

9. Chapter 7: Server-Side Composition

10. Chapter 8: Edge-Side Composition

11. Chapter 9: Client-Side Composition

12. Chapter 10: SPA Composition

13. Chapter 11: Siteless UIs

14. Section 3: Busy Bees - Scaling Organizations

15. Chapter 12: Preparing Teams and Stakeholders

16. Chapter 13: Dependency Management, Governance, and Security

17. Chapter 14: Impact on UX and Screen Design

18. Chapter 15: Developer Experience

19. Chapter 16: Case Studies

20. Other Books You May Enjoy

Packt is searching for authors like you

Basics of server-side composition

A server-side composition implementing micro frontends requires a central point in the backend where the micro frontends are resolved and merged. The basic principle is shown in the next diagram:

Figure 7.1 – The idea behind server-side composition – a central server joins the different frontend fragments

In this pattern, teams will either go for full pages or just individual fragments. Fragments can be as large as fully composed parts of a page or as small as UI components with some domain logic.

The shown reverse proxy essentially plays the same role as the aggregation layer introduced in the previous chapter. The difference is that its responsibilities go beyond proxying micro frontends. Therefore, we'll usually refer to this point as a gateway service or a backend for frontend (BFF).

A BFF is a part of the backend that has been introduced only to serve the frontend. Generally, a BFF can be thought...