Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Art of Micro Frontends

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

Arrow left icon
Product type Paperback
Published in Oct 2024
Publisher Packt
ISBN-13 9781835460351
Length 356 pages
Edition 2nd Edition
Arrow right icon
Author (1):
Arrow left icon
Florian Rappl Florian Rappl
Author Profile Icon Florian Rappl
Florian Rappl
Arrow right icon
View More author details
Toc

Table of Contents (27) Chapters Close

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 26. Other Books You May Enjoy

User experience

One of the key differences between microservices and micro frontends is that the latter needs to appear as a single unit to the end user. This requirement impacts not only the visual design but also behavior and wording. If every part of the frontend is independently developed and maintained, how can we ensure that a single coherent application is presented to the user?

Wording

If we think of the micro frontends as molecules consisting of atoms, we could try to harmonize the situation by aligning available atoms. Here, atoms would be represented as components such as a form, a card, or a text field. Standardizing these would certainly help but would still leave out a design vision or specific wording.

As it turns out, there is no silver bullet here. In the end, it’s a trade-off between centralization and independence. Where we define the point for our application is up to us. For wording, one option is to do the following:

  • Put a set of shared...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image