Everybody is talking about slicing up the monolith. The goal is to create scalable architectures. But how can we achieve that? We’ll discuss the benefits and tradeoffs of micro frontends, implement a basic example, have a look at the Mosaic9 stack and talk about organizational challenges.
Micro frontends: The Good 😻The Bad 😼and The Ugly 🙀
Everybody is talking about slicing up the monolith. The goal is to create scalable architectures. But how can we achieve that?
Project: Create something scalable
New kind of bugs
When implementing standalone, self-contained verticals a lot of things we developers learn in university and in books, should not be applied to this architecture. We shared code where we shouldn’t have shared it.
So many questions
But there is more to talk about. Complex problems need complex solutions. But no micro frontend framework will be able to increase the developer experience before one has understand how they work in general. In this talk, I will start a basic example with iFrames before rushing into difficult frameworks. Armed with that knowledge, I will present Zalando’s Mosaic9 project. It’s an open-source framework for creating a complex micro frontend architecture. After understanding the technical setup of micro frontends, what about the organizational setup? In which vertical does which micro frontend belong to? How to manage the UI Component Library in different teams? Can we switch teams?
Now it seems like micro frontends sound like a bad idea. Complicated, complex, over-engineered? What do we gain from them? Freedom. Autonomous teams. Less meetings and E-Mails. An always deployable master branch.