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

Shift-left approach for testing and security

A shift-left approach should be adopted early in the development life cycle of microservices applications. In a shift-left approach, you bring different activities (security, testing) into the development cycle earlier on to improve the quality of the application.

For example, if you are building a new application, you should test the security of the application in the design phase, by using tools such as Microsoft Threat Modeling. Moving forward, during development, the code should be security scanned using static application security testing (SAST), and furthermore, when the application is deployed, it should be tested using dynamic application security testing (DAST) tools.

The following aspects are important to consider when evaluating this factor:

  • Do you follow a practice of implementing unit tests?
  • Do you follow a practice of evaluating your architecture at the design phase?
  • Do you have any tools to measure...