Develop microservice-based enterprise applications with expert guidance to avoid failures and technological debt with the help of real-world examples 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. 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.
Dropped this after a chapter on Event Storming. Here is the first sentence from that chapter: "Event storming is a workshop-based methodology that is very effective at helping you to quickly gain an understanding of business workflows and obtain a deeper knowledge of the business domain in order to deploy software that meets the needs of the business. ". And then, outside of this nominee for the longest useless sentence ever, there is nothing in the whole paragraph about how event storming actually works.
The book is quite good overview of patterns that are used in microservices architectures. Despite it includes a large portion of Azure examples, you still can get valuable technology-agnostic insights. Just don't pretend to make this book your only reference on the topic. Consider it as an overview of points that you can learn deeper using other sources.