Chapter 6. Micro-Frontend Automation
In this chapter, we discuss another key topic for distributed systems like micro-frontends: the importance of a solid automation strategy. The microservices architecture adds great flexibility and scalability to our architecture, allowing our APIs to scale horizontally based on the traffic our infrastructure receives. This enables us to implement the right pattern for the right job rather than applying a common solution to all our APIs, as in a monolithic architecture. Despite these great capabilities, microservices increase the complexity of managing the infrastructure, requiring an immense number of repetitive actions to build and deploy them. Any company embracing the microservices architecture, therefore, must invest a considerable amount of time and effort in its continuous integration (CI) or continuous deployment (CD) pipelines—which we explore further in this chapter. Given how quickly a business can change direction nowadays, improving a CI/CD pipeline is not only a concern at the start of a project; it’s a constant incremental improvement throughout the entire project life cycle. One of the key characteristics of a solid automation strategy is that it creates confidence in the replicability of artifacts and provides fast feedback loops for developers.
This is also true for micro-frontends. Having solid automation pipelines will enable our micro-frontend projects to succeed, creating a reliable solution for developers to experiment, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access