This chapter covers:
- Solving common asset loading challenges in a micro frontends context.
- Comparing techniques to deal with cacheability and synchronization when loading assets of different teams.
- Deciding what bundling strategy is appropriate: Many smaller bundles or fewer large ones.
- Understanding how on-demand loading can be effectively used with micro frontends.
In the last chapters, we covered a lot of different integration techniques. But we always focused on the content - integrating markup on the server and in the client. A topic we only discussed in passing is: How to load the assets associated with a micro frontends? In this chapter, we’ll dive deeper into this significant side-topic. There are at least a handful of aspects that you must consider. How can we ensure that teams can deploy a micro frontend and the needed assets on their own? How do you implement cache-busting to improve cacheability without introducing tight coupling? How do you ensure that the loaded CSS and JS always fits the server-generated markup? How coarse or fine-grain should your bundles be? Do you want one big bundle for your application, one per team, or even smaller ones? How can on-demand loading techniques help in reducing the upfront asset data the browser needs to process?