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

Chapter 9: Skipping Testing

Why do development teams skip testing? What reason could you have to not test your software? Well, testing is a boring topic for many and something that some folks would rather put off to the last minute. You will hear people say things such as "I just don't have time." Some people blame the business for not wanting to spend the man-hours on testing software, so they never get around to it, or testing gets kicked down the road to the night of deployment. I believe if the business really understood the cost of bugs and the risk of deploying software with bugs, then it would conclude that time must be made for testing software early and often. If you ever want to get the business to listen, then you must place a dollar value on whatever you are trying to get them to understand, be it unit testing, software testing, or adopting agile processes. Businesses are primarily motivated by making and saving money and a solid software testing strategy...