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

Bounded contexts

As we build microservices, we align them to a bounded context, and those bounded contexts align with a particular domain model. The bounded context makes up the components of the domain model, from the database scheme to behaviors and domain objects. Each bounded context has its own UL, its own model, and sub-models.

As we can see once again, a bounded context aligns with microservices, as each bounded context can be one microservice or a collection of microservices.

Once we define our bounded context, we need to better understand how they are related, and we can do this with a very loose sketch known as a context map, as demonstrated in Figure 2.6.

Context maps

To understand the relationships between our bounded context and how they fit together in the bigger picture, we create a context map. This map is a great communication tool for development teams as it helps facilitate a conversation about technical, tactical, and integration issues. A context map...