Neutralizing the benefits of microservices by adopting a frontend monolithic architecture

In the microservices world, the focus has been on converting large monolithic backends into self-contained microservices, managed by separate teams to gain agility. These days, many microservices use feature-rich browser implementations to expose business functionalities to their end users. Mostly, there is a separate team that's responsible for building application user interfaces by consuming APIs exposed by microservices. Over time, these frontends grow in complexity, resulting in a frontend monolithic UI. Hence, the benefits of microservices are somehow constrained due to the architectural style that's followed at the start. To overcome this challenge, you should introduce a plug-and-play architecture, where each team can build their own frontends. Figure 3.1 depicts a monolithic frontend that interacts with multiple microservices. To incorporate multiple microservices, frontend...