Building Microfrontends Part I — Creating small apps
When your front-end starts getting too big, you will want to split it in smaller parts and give each part to a different team to develop, but at the end, they all need to integrate somehow in the same front-end so the user can see it.
This blog post series was built on top of the thoughts produced by Zalando’s Project Mosaic, Open Table’s Open Components and my own experience.
The goal of this series is to be a hands-on guide for creating a Microfrontend Architecture from scratch, at the end you will have 5 containers running, with apps communicating with each other in an architecture that allows scalability.
Most of the time, I’ll be referring to web development here, but maybe those ideas also apply to desktop apps (like spotify's) or mobile apps. If you have more experience with those, please let me know.
Also, as you will note along the way, this is not only a technological problem, but also a communication one. Teams have to communicate well with each other in order to get this kind of architecture working, but I'll focus more on the tech part of it.
November 14, 2018 at 3:11:15 PM UTC
- permalink
-
-
https://medium.com/@_rchaves_/building-microfrontends-part-i-creating-small-apps-710d709b48b7