Book Image

Embracing Microservices Design

By : Ovais Mehboob Ahmed Khan, Nabil Siddiqui, Timothy Oleson
Book Image

Embracing Microservices Design

By: Ovais Mehboob Ahmed Khan, Nabil Siddiqui, Timothy Oleson

Overview of this book

Microservices have been widely adopted for designing distributed enterprise apps that are flexible, robust, and fine-grained into services that are independent of each other. There has been a paradigm shift where organizations are now either building new apps on microservices or transforming existing monolithic apps into microservices-based architecture. This book explores the importance of anti-patterns and the need to address flaws in them with alternative practices and patterns. You'll identify common mistakes caused by a lack of understanding when implementing microservices and cover topics such as organizational readiness to adopt microservices, domain-driven design, and resiliency and scalability of microservices. The book further demonstrates the anti-patterns involved in re-platforming brownfield apps and designing distributed data architecture. You’ll also focus on how to avoid communication and deployment pitfalls and understand cross-cutting concerns such as logging, monitoring, and security. Finally, you’ll explore testing pitfalls and establish a framework to address isolation, autonomy, and standardization. By the end of this book, you'll have understood critical mistakes to avoid while building microservices and the right practices to adopt early in the product life cycle to ensure the success of a microservices initiative.
Table of Contents (16 chapters)
1
Section 1: Overview of Microservices, Design, and Architecture Pitfalls
6
Section 2: Overview of Data Design Pitfalls, Communication, and Cross-Cutting Concerns
10
Section 3: Testing Pitfalls and Evaluating Microservices Architecture

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...