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

The shift-left testing strategy

Testing earlier and often is the idea behind shift-left testing. By moving testing to earlier in the development life cycle, we will prevent errors from being found later in the process or, worse yet, after deployment into production. Shift-left testing moves testing into the development and build phase, which allows the team to detect defects and bugs early on. This allows the team to address and fix these issues faster and before they can do any real damage.

The shift-left testing approach to software testing greatly enhances the deployment and release process, allowing for faster releases that can occur daily, weekly, or even hourly in some cases.

The lack of testing or not implementing testing properly can lead to defects and bugs being deployed into production, which leads to expensive bug fixes and delays in the releasing of new features.

Let's look at some best practices and strategies in the following sections that will assist...