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

Chapter 2: Failing to Understand the Role of DDD

It could be argued that an anti-pattern when building microservices is not having a deep understanding of the business domain or the problem space and then trying to implement microservice tactical patterns. This can lead to chaos or a large, distributed monolith that is tightly coupled and overly complex.

Microservices are collections of services that are designed to meet a common goal or serve a particular business feature. Microservices must work together to meet this common goal. In some cases, a service may be completely unaware of its role when it comes to the bigger picture or may not have knowledge of any other microservices. On the other hand, the teams that build these services should understand the bigger picture and how each service helps achieve the greater goal of the system as a whole or where their service fits in the composition of a larger application.

In this chapter, we will re-examine the characteristics...