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 keeping a single shared database

The number one mistake that teams make when deciding to go with microservices is trying to share a single database and scheme with multiple microservices. So, why is this such a bad idea even though it certainly seems easier? Well, let's start with the definition of microservices.

The definition of a microservice states that each microservice should have its own database or data store for which it is responsible for maintaining the state of its data. Therefore, it makes sense that we adhere to this principle of a single database when creating our microservices. It is also reasonable to conclude that when we break up a monolithic application into microservices, we must break apart the large monolithic legacy database into smaller, separate data stores of one per microservice. This breaking up of mature legacy databases is no easy task and should not be taken lightly. An activity such as breaking up a mature database into smaller...