Member-only story
ARTICLE
Which Technique/Architecture is right for my Project?
From Micro Frontends in Action by Michael Geers
This article covers:
• Contrasting the difference between a web site and a web app and investigating the implications this has on picking an integration technique.
• Comparing different micro frontend architectures by their benefits and challenges.
- Figuring out the best architecture and composition technique for your project’s needs.
_____________________________________________________________
Take 37% off Micro Frontends in Action. Just enter fccgeers into the discount code box at checkout at manning.com.
_____________________________________________________________
In this article, we go over the terminology and highlight the key advantages of different techniques and architectures. After that, you’ll learn about the Documents-to-Applications Continuum. It’s a concept that helps you with the decision of whether to render your markup on the server, client, or both. This distinction is crucial because it determines which architectures and integration patterns are suitable for your use-case. We’ll end with an architecture decision guide. You’ll learn how you can make a sound choice based on a handful of questions. These questions lead you through the different options.
Revisiting the terminology
When you’re setting up a micro frontends project with different teams, everyone must use the same vocabulary. This is why we take a moment to sort the terms. We’ll start with the basic building blocks: the integration techniques. Then we’ll look at different high-level architectures that you can build with them.
Figure 1 shows several integration techniques.
We can group them into two categories: Page-Transition and Composition. Let’s look at the transitions first.
Page transitions
When we talk about page transitions as an integration technique, we mean inter-team page transitions. How does a user get from a page owned by Team A to a page owned by Team B? From an…
