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

Summary

We started the chapter with an overview of what microservices are and how they pertain to DDD for you to understand their relationship. We also looked at the benefits and challenges of microservices as compared to DDD.

Later, we learned how DDD relates to the characteristics of microservices and that teams need to be aligned to a service, ideally a one-to-one team alignment to a microservice. Each service should have its own code base managed by one team. We learned that we need to take a holistic view of our microservices architecture. We also discussed the Cynefin framework to determine the type of problem we are trying to solve, in order to understand the amount of effort and resources required to build our microservices.

We talked about how each boundary is based on a logical grouping of aggregates that are transaction boundaries and enforce invariants of the domain. We learned that we may not get this right first time and, as our knowledge of the domain deepens...