Microservice Architecture

I used this to prepare for an interview and my mind was blown. After years of building microservices in both startup and corporate environments, I was still learning so much about decoupling services and data in a way that increases system cohesiveness. The authors accurately and comprehensively took apart each of the organizational impediments to the "microservice way", explaining each with real-world examples. Very good read. Anyone trying to increase their influence on their organizations technical trajectory should pick up this book.

If you already know anything about microservices you'd probably hate it but it's a good intro for someone who works with a bunch of nerds who talk about microservices all the time and want to now what the heck they're talking about.

I really like his book. It is short and clear. It explans what MSA is, why and how it came about, and what its main advantages are. It also offers some handy methods/patterns that enable you to deal with situations where microservices have shared data. Very usefull.(The book does not contain any code). I was intrigued by the HyperMedia style, which is a way to make the message based communication between services less fragile. So, I went out and bought the predecessor book "RESTful Web APIs: Services for a Changing World." which supposedly covers this topic in greater deal.

First, I have to say that the book is very well-organized. Second, there are some good points and some chapters are quite strong. However, you could clearly feel that different chapters are written by different people. Some of the chapters were really tedious and not on point. What I found a big NO is the fact that in certain cases it is more about technology than the architectural principle behind it. The most obvious example is Docker. Yes, it is practically THE standard for Microservices, but I would like to hear a critical evaluation of it especially about what it is lacking. The overall Docker talk was very favourable and felt like an advert. I got the book for free at a conference, but I am not sure that the price of 32$ is justified for 100 pages. I would love to see updated version extending on the good points and deviating from technology.

Concise, fast and clear view for both tech and management. Thanks to the authors for this book and the insights.

Good introduction to the microservice way and overall how to handle changes in a service. however there isn't any real example

Like almost all books on this subject matter, and similar subject matters, this book deals with its topics rather superficially. For example, on the topic of an optimal size of a microservice, the book borrows general guidelines from other sources without offering ample concrete evidence for applying the guidelines. It would have been much more satisfactory to offer several examples covering various domains of Microservices and explain why the Microservices were sized as such. However, the book does offer the following: • You can have a system that is both decentralized and governed, but it’ll cost you. • Make sure that Microservices are worth the cost to your organization before you delve into them – other optimizations to your development process may yield more immediate returns. • A good design process is an incremental design process. • It’s not sufficient to have ownership on a per-Microservice basis – the holistic view of the entire system also must have clear ownership. • Teams can and should be allowed to act on their own within safe boundaries established by the leaders. • “Eventual Consistency”, is an empowered, iterative style that is suitable for Microservices. • Capabilities-centric design is more suitable for Microservices than the more traditional data-centric design. • Infrastructure automation and operational maturity are important for Microservices teams. • Microservices are the antidote for the pernicious release coordination overhead. • Linux containers pre-date and are a natural deployment environment for Microservices. • Gateways are quite suitable for both securing as well as routing to Microservices. • Contextual controls may be a happy medium between total centrality and total decentralization.

This is a great read I think the price could be lower but that is just me.

O livro aborda muito bem as características gerais, tanto as técnicas como culturais. Cita as principais tecnologias envolvidas, porém sem se aprofundar muito. Foca mais em apontar as mudanças organizacionais envolvidas no processo de adoção de micro serviços.

As a relative newcomer to u-services, I was hoping for some substance and some insight into adoption and building out a system around u-services. But unfortunately, you don't really get any of this. It's the literary equivalent of click-bait. I was recommended this book by a.n.other, but I guess I should have read the existing reviews more thoroughly.

Un buon libro che introduce molto bene i principi e i concetti legati ad una filosofia di approccio al Microservice, lettura scorrevole nonostante sia in inglese...ovviamente da dei spunti, nessun approfondimento specifico, serve ulteriore documentazione

Ceci dit, j'aurais aimé que les IHMs soient abordées. A savoir : est-il préférable d'avoir un "gros service IHM" qui corresponde au "produit dans son ensemble", façade vers les microservices métier ? Ou bien, une IHM éclatée dans les microservices (mais alors il faut recomposer dans le navigateur...) ? Selon moi, "smaller is better" est difficile à tenir si l'on dit que chaque composant "sert" son IHM. Merci pour cette excellente lecture. --nick

Muy digerible y fácil de entender. Enseña muchas referencias, va orientado más a arquitectos que a desarrollar.