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

Complex or not complex – that is the question

Microservices can be simple, complicated, or complex, and if we do not understand them, we can fall into chaos. So, we can then use a process—or rather, a framework— to help us to decide whether we are dealing with a simple, complicated, or complex situation in order to determine what type of microservice we are building and what level of effort and resources we will need to build that service, be it people, time, or effort. We can determine whether we can buy something off the shelf for simple situations, or we can implement an existing framework. We can also determine whether we need to involve an expert to tell us which frameworks and tools we need and how to configure such tools. Finally, we can determine whether we are dealing with a complex problem and, if so, we need to assign the best people, resources, and efforts to build our microservice.

The following diagram illustrates that different microservices...