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

Not abstracting common microservice tasks

Abstracting microservices is a practice used in the implementation of microservice architecture. Mostly, the abstraction layer sits on the API gateway layer, which provides various cross-cutting concerns for abstracting common tasks. However, there are various tools available in the market that allow abstraction without adding abstraction to the API gateway layer and help with performing common tasks.

Not abstracting microservices seems to be an anti-pattern since it requires learning effort at the team level, plus it introduces challenges concerning the limitations of the underlying technology and the platform you are targeting. For example, let's say you are building a service in the Go language, and the message broker doesn't support the SDK to communicate with that service. In this case, if we can create an abstraction layer that communicates with the message broker, the service will help the team consume it, instead of reinventing...