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

Summary

In this chapter, we learned about various architecture pitfalls while building microservices. We discussed the layered architecture, its complexities, its benefits, and how it can be applied to microservices. We also discussed how entity microservices and nanoservices can lead to complexities in your microservice architecture, all of which can be addressed by implementing different strategies, such as API gateways and aggregator patterns. Which tools, technologies, and frameworks you select should be well-thought-out and discussed as part of the shared governance model across the teams to bring consensus.

Then, we discussed how we can address the architecture intricacies of microservices using Dapr. After, we discussed how having a lack of knowledge about container technologies, orchestrators, and cloud-native platforms can slow down the adoption of microservices and how we can accelerate this adoption by embracing them. Finally, we discussed the drawbacks of monolithic...