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 4: Keeping the Re-Platforming of Brownfield Applications Trivial

  1. The main objective of migrating from monolith to microservices is to enhance scalability and productivity. The application is decomposed into a set of independent services that are easier to maintain and change, embracing agility.
  2. The following are the factors to consider when re-platforming a monolithic application to a microservices architecture:
    • Knowledge of business domains
    • Awareness of the change in infrastructure
    • Choosing the right technology and embracing the learning curve
    • Moving to the cloud
    • Understanding the difference between core microservices and API microservices
    • Avoiding chatty services
    • Ensuring development, delivery, and operation readiness
  3. They are important factors since all of these can bring value to the business. If the application is available and scalable in nature, it can handle all kinds of workloads, ensuring availability to the users. Reliability, on the other hand, helps to...