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

Communication protocol across services

Microservices are independent fine-grained services that communicate with each other across process boundaries, hosted across the network, to address different business use cases. Choosing the right communication protocol is a very important factor to ensure reliable communication. The following aspects should be considered when assessing this factor:

  • Are you following an API-first approach?
  • Do you have deep chaining of services over synchronous communication protocols?
  • Do you have asynchronous communication anywhere in the system?
  • Which message broker technology are you using?
  • What is the throughput of messages received or processed by the services?
  • Do you have direct client-to-microservice communication?
  • Do you need to persist messages?
  • Are you using a materialized view pattern to address the chatty behavior of microservices?
  • Have you implemented a retry pattern, a circuit breaker, exponential back-off...