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

Dapr versus service meshes

Both Dapr and the service mesh offer overlapping capabilities, raising the question of how Dapr compares to a service mesh and when one should be used over the other. While both Dapr and service meshes have the same goal of reducing complexity, their intended audiences are somewhat different. Dapr focuses on improving the developer experience by abstracting your microservices and offering a collection of building blocks to meet common microservices needs, whereas a service mesh helps application operators by providing a network service mesh that addresses networking concerns. Let's take a closer look at the similarities and differences between the two, as listed in the following table:

Table 6.2 – Comparing Dapr and service meshes

So, should you employ Dapr, a service mesh, or a hybrid of the two? Well, the answer depends on your needs. When using both Dapr and a service mesh, it might seem intuitive to activate the...