Understand the key challenges and solutions around building microservices in the enterprise application environment. This book provides a comprehensive understanding of microservices architectural principles and how to use microservices in real-world scenarios. Architectural challenges using microservices with service integration and API management are presented and you learn how to eliminate the use of centralized integration products such as the enterprise service bus (ESB) through the use of composite/integration microservices. Concepts in the book are supported with use cases, and emphasis is put on the reality that most of you are implementing in a “brownfield” environment in which you must implement microservices alongside legacy applications with minimal disruption to your business. Microservices for the Enterprise covers state-of-the-art techniques around microservices messaging, service development and description, service discovery, governance, and data management technologies and guides you through the microservices design process. Also included is the importance of organizing services as core versus atomic, composite versus integration, and API versus edge, and how such organization helps to eliminate the use of a central ESB and expose services through an API gateway.
What You'll Learn Who This Book Is For Developers and DevOps engineers responsible for implementing applications around a microservices architecture, and architects and analysts who are designing such systems
Mix of everything... Before reading I wondered if you can squeeze such big "words" like designing, developing and deploying in one book and still deliver acceptable value. My answer is: no, you can't. Or at least: not this time yet.
What I liked: - nice chapters about integrating microservices, Service Mesh and security (well described OAuth 2.0)
What I didn't like: - authors have tried to make a practical book with many examples in code. In general, it's a great goal. Here however I felt like those examples didn't go anywhere. No concept of bigger problem and solution existed. It was just a number of tutorials about specific technologies. You can do it yourself by visiting each project site / documentation independently (e.g. docker, istio etc.) - I feel that my main questions about microservices are still open - no answers found in this book. I think that designing part is the most challenging and in the most of the cases the least described. This book repeats this pattern. Why we need microservices and what exactly the beneftis are? How properly divide you domain into services? You can't just write that "here you have a customer service and there you have a user service". I totally agree that choice of technologies is reaaaally important but without good design it might be worthless.
Good microservices overview. A little bit on everything. Helps to understand the big picture, trends and complexity. Think twice before jumping into it.
Good introduction to the microservices definitely, scratch the surface for many important topics in microservices domain, I liked two security chapters, further deep readings are required later on
Very good book that gives a really broad perspective on microservices, design principles, patterns, anti-patterns etc. It doesn't go into the details, but there are mentioned a lot of technologies which are being used in the scope of microservice architecture. A little bit of everything: this book will help you understand the big picture of microservices but you will not know how to implement details after reading it. There are also useful code examples for Spring Boot. The writing style of author is really clear, unambiguous and rhetorically amazing!