Embracing Microservices Design: A practical guide to revealing anti-patterns and architectural pitfalls to avoid microservices fallacies

Develop microservice-based enterprise applications with expert guidance to avoid failures and technological debt with the help of real-world examples

Key Features

• Implement the right microservices adoption strategy to transition from monoliths to microservices
• Explore real-world use cases that explain anti-patterns and alternative practices in microservices development
• Discover proven recommendations for avoiding architectural mistakes when designing microservices

Book Description

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.

What you will learn

• Discover the responsibilities of different individuals involved in a microservices initiative
• Avoid the common mistakes in architecting microservices for scalability and resiliency
• Understand the importance of domain-driven design when developing microservices
• Identify the common pitfalls involved in migrating monolithic applications to microservices
• Explore communication strategies, along with their potential drawbacks and alternatives
• Discover the importance of adopting governance, security, and monitoring
• Understand the role of CI/CD and testing

Who this book is for

This practical microservices book is for software architects, solution architects, and developers involved in designing microservices architecture and its development, who want to gain insights into avoiding pitfalls and drawbacks in distributed applications, and save time and money that might otherwise get wasted if microservices designs fail. Working knowledge of microservices is assumed to get the most out of this book.

Table of Contents

1. Setting up the mindset for Microservices endeavour
2. Failing to understand the role of DDD
3. Microservices Architecture Pitfalls
4. Keeping re-platforming of brownfield applications trivial
5. Data Design Pitfalls
6. Communication pitfalls and prevention
7. Cross Cutting Concerns
8. Deployment Pitfalls
9. Skipping Testing
10. Evaluating Microservices Architecture

Ovais Mehboob Ahmed Khan is a seasoned programmer and solution architect with nearly 20 years of experience in software development, consultancy, and solution architecture. He has worked with various clients across the world and is currently working as a senior customer engineer at Microsoft. He specializes mainly in application development using .NET and OSS technologies, Microsoft Azure, and DevOps. He is a prolific writer who has written several books and articles on various technologies. He really enjoys talking about technology and has given a number of technical sessions around the world. Nabil Siddiqui is an open source contributor and technology speaker who is currently working as a cloud solution architect at Microsoft, focusing on application innovation. He is well versed as a software engineer, consultant, trainer, and architect. He has around 20 years of experience, ranging from desktop applications to highly distributed applications on different platforms using various programming languages. During his career, he's accomplished various technical challenges and worked on a broad range of projects that have given him rich experience in designing innovative solutions to solve difficult problems. Tim Oleson, a customer engineer at Microsoft, focuses on domain-driven design, CosmosDB, Microsoft Azure PaaS, and Azure Kubernetes Service. He is a seasoned software engineer, consultant, trainer, and architect. He has 20+ years of experience, ranging from web applications to highly distributed service-oriented applications.