13 Teams and boundaries

 

This chapter covers:

  • Structuring your teams to maximize the benefits of the micro frontends architecture
  • Fostering a healthy amount of knowledge-sharing between the teams
  • Identifying common crosscutting concerns and highlighting different strategies to address them
  • Illustrating the challenges a diverse technology landscape can introduce
  • Helping new teams to get up and running quickly

Throughout this book, we’ve focused on the technical aspects of micro frontends. You learned techniques to integrate independent user interfaces that form a greater whole. We talked about strategies to mitigate architecture-inherent issues like performance and providing a seamless user interface. But why are we doing all this?

Yes, there are some technical benefits that come with this architecture. Smaller software projects are simpler to build, test, understand, and rebuild than a monolith. Being able to use different tech stacks in different areas of the product can also be a valuable asset.

However, the most significant benefits our composable frontend architecture unlocks are the organizational ones. It makes it possible to parallelize development. Properties like having real team ownership and local decision making can lead to faster innovations.

13.1 Aligning systems and teams

13.1.1 Identifying team boundaries

13.1.2 Team depth

13.1.3 Cultural change

13.2 Sharing knowledge

13.2.1 Community of practice

13.2.2 Learning and enabling

13.2.3 Present your work

13.3 Cross-cutting concerns

13.3.1 Central infrastructure

13.3.2 Specialized component team

13.3.3 Global agreements and conventions

13.4 Technology diversity

13.4.1 Toolbox and defaults

13.4.2 Frontend blueprint

13.4.3 Don’t fear the copy

13.4.4 The value of similarity

Summary

sitemap