Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Embracing Microservices Design
  • Toc
  • feedback
Embracing Microservices Design

Embracing Microservices Design

By : Mehboob Ahmed Khan, Siddiqui, Timothy Oleson
4.6 (14)
close
Embracing Microservices Design

Embracing Microservices Design

4.6 (14)
By: Mehboob Ahmed Khan, 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)
close
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

Chapter 6: Communication Pitfalls and Prevention

  1. In synchronous communication, the client sends a request and waits for a response from the service. Synchronous communication can be blocking or non-blocking, but the client can only continue further processing once the response is received from the service. In asynchronous communication, the client sends a message to the message broker that acts as middleware between the client and service. Once a message is published to the message broker, the client will continue processing without waiting for the response. The service can subscribe for specific messages to the message broker and place responses back in the message broker after processing. Both the client and service are unaware of each other and can continue to evolve without any dependency. 
  2. Direct client-to-microservice communication introduces tight coupling between the client and microservice, where clients need to be aware of how different microservices...
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete