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

Knowing how to perform reporting

Reporting is important to the business; to be able to analyze and monitor business outcomes, we must have a good reporting strategy. In most cases, reporting with monolithic applications and databases is a straightforward process. All we do is write stored procedures with complex joins and aggregates on the data to create views of the data. This is not possible in a distributed world; we do not have access to joins as the data is physically separated. So, how do we carry out these complex joins in a distributed microservice architecture? Well, the answer to that question is that we carry out the joins on the application layer in memory, not on the data layer. These joins are conducted in a reporting service using an API composition pattern.

The API composition pattern

A composition pattern calls each of the respective query services of each microservice that queries the database. Then, the API Composer service executes the joins on the data in...