Microservices can also be integrated with a web front-end. Dividing the front end into different modules helps to solve some of the problems that come from treating it as a monolith. A modularized front-end is made up of separately deployable microservices. This can bring many benefits to your front-end.

For example, a modularized frontend can have independent domain logic, and a change in the domain can be implemented simply by modifying only one microservice. To combine separate front-ends, they must be integrated, so an integration system is necessary.

Front-end Monolith divided into Modules

This can be accomplished through links, where one frontend displays a link that another frontend reads and handles. This can also be accomplished through redirects, for example, how OAuth2 handles frontend integration. Redirects combine data transfer with frontend integration.

There are, however, a few exceptions when a frontend should be deployed as a monolith. For example, native mobile applications should be deployment monoliths, or if there were a singular team responsible for frontend development.