You're reading from The Art of Micro Frontends Build highly scalable, distributed web applications with multiple teams

Product type Paperback

Published in Oct 2024

Publisher Packt

ISBN-13 9781835460351

Length 356 pages

Edition 2nd Edition

Concepts

Front End Web Development

Author (1):

Florian Rappl

View More author details

Table of Contents (27) Chapters

Preface

1. Part 1:The Hive – Introducing Frontend Modularization FREE CHAPTER

2. Chapter 1: Why Micro Frontends?

3. Chapter 2: Common Challenges and Pitfalls

4. Chapter 3: Deployment Scenarios

5. Chapter 4: Domain Decomposition

6. Part 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. Part 3: Bee Brood – Implementation Details

15. Chapter 12: Sharing Dependencies with Module Federation

16. Chapter 13: Isolating CSS

17. Chapter 14: Securing the Application

18. Chapter 15: Decoupling Using a Discovery Service

19. Part 4: Busy Bees – Scaling Organizations

20. Chapter 16: Preparing Teams and Stakeholders

21. Chapter 17: Dependency Management, Governance, and Security

22. Chapter 18: Impact of Micro Frontends on UX and Screen Design

23. Chapter 19: Building a Great Developer Experience

24. Chapter 20: Case Studies

25. Index

Why subscribe?

26. Other Books You May Enjoy

The evolution of web applications

Before looking for reasons to use micro frontends, we should look at why micro frontends came to exist at all. How did the web evolve from a small proof of concept (POC) running on a NeXT computer in a small office at Conseil Européen pour la Recherche Nucléaire (CERN)/The European Organization for Nuclear Research to become a central piece of the information age?

Programming the web

My first contact with web development was in the mid-1990s. Back then, the web was mostly composed of static web pages. While some people were experienced enough to bring in some dynamic websites using the Common Gateway Interface (CGI) technology, as shown in Figure 1.1, most webmasters did not have knowledge of this or wanted to spend money on server-side rendering (SSR). The term webmaster was commonly used for somebody who was in charge of a website and instead of doing SSR, everything was crafted by hand upfront.