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

An incredible resource if you’re looking to get into the world of microservices from the experts themselves!!

I received this book as a gift from a friend. This book mainly focuses on microservices architecture, pitfalls, anti-patterns, challenges related to its design, architecture, and adoption of microservices whether you are founding microservices from the scratch or refactoring existing monolith to microservices architecture. If you want to grasp microservices regardless of whether you have prior working experience or totally new to this arena, this book is for you.Here is some core focus of this book:This book starts with the outlook and benefits of the microservices architecture and what are some components (state management, API gateway, orchestration, messaging) and challenges its design. How cloud-native can play an important role in microservices architecture with the help of twelve-factor design principles.Why DDD (Domain Driven Design) plays a vital role in the implementation and success of microservices. Taking advantage of DDD for collaboration among the stakeholders and toward the defining microservices bounded context.Architecture pitfall and different complexities and how to deal with those with tools in the adaption of microservices and how team knowledge of cloud Native, orchestration, and choosing the right tools can help in the adoption of microservices.Pitfalls and considerations while transferring a monolith app into microservices and why should give importance to availability, scalability, and reliability during those transitions.Distributed transactions in the context of microservices architecture and how to tackle them.Microservice communication patterns, common protocols, pitfalls like direct communication of frontend with microservices how to avoid with help of API gateway.Focus on non-functional requirements security, logging, metrics, resilience, tracing, translation, and discovery with help of chassis and gatekeeper pattern.Deployment plan and roll back and plan and strategy. It also discusses the role of new technology like IaaC (Infrastructure as Code), DevOps, CI/CD, Agile Process, and Kubernetes.Importance of the various types of testing in the context of microservices and skip testing antipatterns.Though some sections of the book discussed the Azure cloud components, I think someone can understand or can find what is the counterpart in other Cloud platforms. I must say the authors did a great job setting up the attitude and understanding of microservices architecture and its challenges. So that you are ready during your journey toward the microservices architecture.

I've recently embarked on a review of literature on microservices and modern cloud architecture that has been published over the last 18 months or so. My goal is to find useful references and teaching aids to introduce new team members in my current workplace to this area of architecture. A lot has come out in 2020 and 2021.Embracing Microservices and Design (reviewing the hardcover version) takes an interesting approach. Chapter 1 focuses on definitions and first principles... not just of the architecture itself, but also how it impacts the organization that implements the approach on the business and org design side of things. It also grounds the evolution of the architecture in the 12-factor ++ approach (adding the common 3 additions that have come into favor in recent years).From there, each chapter in Section 1 approaches an aspect of the microservice approach through the lens of anti-patterns and pitfalls that commonly entangle teams.This ranges from not understanding design approaches (e.g. DDD), to the nuance of simplicity through some added complexity.Section 2 of the book following a similar agenda of identifying problems you may encounter when considering data, communication, and shared core technology aspects of a system.Section 3 focuses on the tooling and testing aspects of microservices, again looking at issues and their solutions/workaround/signals. It is here you get a brief view of DevOps issues, monitoring, CI/CD, and automated testing... all critical needs in a Continuous Deployment methodology most commonly used working with this architecture.Overall, I liked the approach of starting with problems, constraints, errors, and wrong roads traveled. This presents and interesting balance to what I consider some of the best recent microservices books from authors like Sam Newman. The approach does take a little getting used to though, and I'm not sure how easy it would be to use as a reference if you are looking to jump to the best practice first.I appreciate the expertise of the authors and they are clearly coming from an MS Azure world, and the one star I'm knocking here is that I really with the patterns and solution examples/suggestions were a little more cloud platform neutral. I get it, from the perspective of their employer being Microsoft, but even would have loved more Open Source exploration (don't get me wrong, there is plenty...e.g. K8s, Envoy, Dapr, etc). I'd love to have similar suggestions for AWS and GCP too, though.Generally, I'd recommend this reference as a supplement to the many good Cloud Native and Microservice books now out in print.

This is well organized and well written book on Microservices. Not your usual cup of tea, as it points to the pitfalls and reasons why some of the organizations fail to implement the microservices architecture correctly in the first place. Great deal for anybody who is diving into the world of microservices. Very well organized, while there are not many - great illustrations when needed and brings out the most important concepts when it comes to the topic and how to avoid problems when implementing them. Highly recommended read from these authors!!!

It is a good book for the cloud architect. The authors do a good job of describing the limitations and strengths of various architectures. In particular, the book is not tied to any particular technology or vendor. This book can be used as a tutorial or as a reference book for designing microservice architectures. I liked the discussion about performance regarding various choices.

1.) Heavy focus on avoiding pitfalls so you don't have to learn microservices the hard way.2.) Lays out the key principles and reasoning behind DDD3.) Walks you through real-world scenarios and how to execute a successful, secure deployment.4.) Relevant for any software engineer or app developer working in or around a DevOps environment.