Slicing your application into micro frontends

To maximize gains from the micro frontend architecture and minimize the risks defined in the previous section, we need to create microservices that are as independent as possible and that make sense for your team’s organization.

The most common type of project organization is the verticalization of functionalities – that is, for one project you might have an entire user journey, such as a product purchase screen, another project for product registration, and another for the administration module of the application.

Figure 11.1 – Micro frontend division

This diagram exemplifies the concept of division using an Angular application. In each project, we have all the components for the user experience.

You may be wondering, “Can I achieve this same separation using Angular modules?” and the answer is yes, you can. If a team takes care of all the modules for your company&...