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

End-to-end testing

Before we deploy our microservices into production, we need to have a high level of confidence that it will not cause an issue with other services or infrastructure. Although end-to-end testing has value, careful consideration must be given when employing this type of testing as it is difficult to do and costly in terms of time and resources.

We need to be confident that the microservice is behaving as expected. We need to write a test that verifies that the service in question is interacting with infrastructure services and other application and domain services. To successfully test all of these interactions, we need all the services and databases involved to be up and running in an appropriate environment.

End-to-end tests are slow and brittle and can be costly in terms of time and maintenance. End-to-end testing should be minimized and represents the smaller portion of our testing pyramid, as shown in Figure 9.1.

The best strategy for end-to-end testing...