Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
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 websites using compositional UIs that grow naturally as your application scales

Arrow left icon
Product type Paperback
Published in Jun 2021
Publisher Packt
ISBN-13 9781800563568
Length 310 pages
Edition 1st Edition
Languages
Tools
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 (21) Chapters Close

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

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 does not only impact the visual design but includes 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 the 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