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

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. 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

A healthcare management solution

OpenMRS is a collaborative open source project that helped create electronic medical record (EMR) software. It was first released in May 2014 and was originally written in Java.

OpenMRS, Inc. is a registered non-profit company that is the owner of all project-related intellectual property and the maintainer of the software’s public license. The entity also represents the project in legal and financial matters.

Overall, the project has about 200 permanent contributors divided into a dozen teams. The development is mostly done on GitHub, with project management being centralized on Jira.

Problem description

The project’s ecosystem was huge. While the backend provided a mechanism that could be extended in the form of Java modules, the frontend was often considered a necessary evil and was either reimplemented or replaced by a suitable alternative.

One problem here was that many distribution creators wanted to have a SPA experience...