This chapter covers:
- Examining how to measure performance when multiple micro frontends exist on one page
- How to find regressions and bottlenecks and attribute them to the right team
- Typical performance drawbacks that are consequential to the micro frontends architecture
- Implementing library sharing without compromising team independence
In 2014 my colleague Jens handed me an article 1 written by a company that implemented a vertical style architecture. Back then, the term micro frontends didn’t exist. Being a frontend developer who takes pride in delivering fast user experiences, my first gut reaction to this idea was rejection--strong rejection. “Five teams that all roll their own frontend? This sounds like a lot of overhead. The result will surely be inefficient and slow.”
1 S. Kraus, G. Steinacker, O. Wegner. “Teile und Herrsche: Kleine Systeme für große Architekturen,” OBJEKTspektrum 05/2013 (German), http://mng.bz/xWDg.