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

The pitfalls of not knowing how to handle transactions

One pitfall that teams face is not knowing how to handle transactions that are distributed across multiple microservices. We will explore how we can frame transactions within a microservice and how to handle them when they involve multiple microservices. We will start with a concept that we explored in Chapter 3, Microservices Architecture Pitfalls, where we discussed domain-driven design and the concept of aggregation.

Aggregates are transactional boundaries. They form boundaries around transactions that enforce business rules and business invariants. These are then grouped by relevant entities that are part of the aggregate and its transactional boundary. These transactions are a single unit of work and can be made up of multiple operations that live in the space of that isolated transaction and produce a domain event that represents a state change to the aggregate and its internal entities. A command is an operation that...