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

Not considering Infrastructure as Code (IaC) for environment setup

Setting up the environment is an essential activity to be carried out to deploy any application. Many companies have strategies for creating multiple environments, such as staging, canary, and production to help deploy their workloads for testing and going live. Infrastructure as Code (IaC) provides a platform for creating the script for your infrastructure and deploying it to as many environments as necessary. Imagine that you manually set up an infrastructure that takes 5 days to complete for a single environment, while replicating it for other UATs, staging, and performing a canary deployment needs an additional 15 days. Moreover, if any part of the environment crashes, resetting would take the same time again. With IaC, since the whole configuration is written in the form of a script, you can deploy in minutes and easily replicate to multiple environments.

Azure Resource Manager (ARM), from Microsoft, and Terraform...