What do you think?
Rate this book
Microservice Architecture: Aligning Principles, Practices, and Culture
Microservices can have a positive impact on your enterprise just ask Amazon and Netflix but you can fall into many traps if you don t approach them in the right way. This practical guide covers the entire microservices landscape, including the principles, technologies, and methodologies of this unique, modular style of system building. You ll learn about the experiences of organizations around the globe that have successfully adopted microservices.In three parts, this book explains how these services work and what it means to build an application the Microservices Way. You ll explore a design-based approach to microservice architecture with guidance for implementing various elements. And you ll get a set of recipes and practices for meeting practical, organizational, and cultural challenges to microservice adoption.Learn how microservices can help you drive business objectivesExamine the principles, practices, and culture that define microservice architecturesExplore a model for creating complex systems and a design process for building a microservice architectureLearn the fundamental design concepts for individual microservicesDelve into the operational elements of a microservices architecture, including containers and service discoveryDiscover how to handle the challenges of introducing microservice architecture in your organization
144 pages, Paperback
Published August 30, 2016
95 people are currently reading
274 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 26 of 26 reviews
September 19, 2016
very high-level imho - for CTOs, or something like - more about organization & culture, not about the technical stuff.
For technical things the Building Microservices is better...
For technical things the Building Microservices is better...
April 17, 2022
This dementor of a book was stealing my soul so I kicked it to the curb finally....!!!!! :D
So this book is a bit of a bore and maybe not a good read for a software engineer. As many other reviewers have pointed out this talks about microservices at a very high level and doesn't really add up to much. Read about half of it and didn't feel like continuing..
So this book is a bit of a bore and maybe not a good read for a software engineer. As many other reviewers have pointed out this talks about microservices at a very high level and doesn't really add up to much. Read about half of it and didn't feel like continuing..
May 23, 2017
Not a bad book for a starter. It has a high-level approach on Microservices and gives you enough insight to get curious or want to read more.
It is not meant for developers but CTOs, managers and some high-level architects (city planners). Therefore if you are interested in how to actually build microservices: choose another title.
It is not meant for developers but CTOs, managers and some high-level architects (city planners). Therefore if you are interested in how to actually build microservices: choose another title.
February 17, 2019
This is a good book about microservice architecture. It introduces some of the concerns that first-time implementers often have, along with practical realities.
Book has good solution architecture guidance, organizational guidance, culture guidance, tools and process guidance, service design guidance. It also introduces very useful tools.
Books also talk about culture that I think it is an important things when you want to implement microservice architecture.
Book has good solution architecture guidance, organizational guidance, culture guidance, tools and process guidance, service design guidance. It also introduces very useful tools.
Books also talk about culture that I think it is an important things when you want to implement microservice architecture.
March 11, 2018
Microservice Architecture: Aligning Principles, Practices, and Culture is definitely a managerial book that is approachable by non-technical people.
However I highly advise being technical due to the hype being "sold" to you.
I am not against microservices but this book, at the time of writing, which is 2016th, is selling some pros of microservice "macro" architecture a bit too optimistically. This is the danger of writing for the hype. At 2015-2016th in my opinion, except for Twitter and Netflix (among popular companies), nobody was changing purely to microservices. Yet it can lead to the "deathstar architecture" as seen in https://twitter.com/alxspb/status/626....
So, while microservices are great, the book preaches mostly the pros, which at this point most of the readers know already, to name a few:
* independent releases,
* much easier parallel development,
* much more manageable scrum sprint cycles due to the smaller codebase,
* and of course, separation of concerns.
But in practice microservices are no silver bullet. They require a lot of discipline in service communication, message protocol and in general API design and maintenance, monitoring, testing, orchestration and much more. If you're used to end-to-end testing, you're going to have the fun of your life (or what is left of it after slowly deteriorating) when you try to find a problem in a specific service. This is manageable with few microservices, but depending on the scale, complexity of the business, over-engineering of the services and perhaps going too far with separation of concerns, can lead to more issues. Definitely check out https://testing.googleblog.com/2015/0... where not even "micro" is mentioned, but the concept applies.
What the verdict here is, don't just switch to microservices over a book, hype, trend.
Focus on your business' needs, knowledge and visibility of the technical issues you have in your organization and make a mature decision. Perhaps starting with new low-risk services and starting a microservice architecture in a limited business domain is better.
All and all, the book doesn't really show the risks and cons. It's a green path
However I highly advise being technical due to the hype being "sold" to you.
I am not against microservices but this book, at the time of writing, which is 2016th, is selling some pros of microservice "macro" architecture a bit too optimistically. This is the danger of writing for the hype. At 2015-2016th in my opinion, except for Twitter and Netflix (among popular companies), nobody was changing purely to microservices. Yet it can lead to the "deathstar architecture" as seen in https://twitter.com/alxspb/status/626....
So, while microservices are great, the book preaches mostly the pros, which at this point most of the readers know already, to name a few:
* independent releases,
* much easier parallel development,
* much more manageable scrum sprint cycles due to the smaller codebase,
* and of course, separation of concerns.
But in practice microservices are no silver bullet. They require a lot of discipline in service communication, message protocol and in general API design and maintenance, monitoring, testing, orchestration and much more. If you're used to end-to-end testing, you're going to have the fun of your life (or what is left of it after slowly deteriorating) when you try to find a problem in a specific service. This is manageable with few microservices, but depending on the scale, complexity of the business, over-engineering of the services and perhaps going too far with separation of concerns, can lead to more issues. Definitely check out https://testing.googleblog.com/2015/0... where not even "micro" is mentioned, but the concept applies.
What the verdict here is, don't just switch to microservices over a book, hype, trend.
Focus on your business' needs, knowledge and visibility of the technical issues you have in your organization and make a mature decision. Perhaps starting with new low-risk services and starting a microservice architecture in a limited business domain is better.
All and all, the book doesn't really show the risks and cons. It's a green path
December 27, 2016
My first book about microservices and clearly, a bad choice. The reason why I'm not upset is, that I've received the book for free (as present on GeeCON conference).
Why a bad choice? Well, I'm not a CTO, or similar kind of managerial decision maker; who are probably the target group of this book. I'm just an architect/developer/technical leader and for me, there was too much fillers and repetitions and marketing/vision/business stuff & fluff.
Slightly interesting is the technical part, or rather "technical" (still not specific enough for my level), which inspired me to study some interesting tools/technologies, like Swagger, or Docker.
Feel free to suggest some better book about microservices in comments.
Why a bad choice? Well, I'm not a CTO, or similar kind of managerial decision maker; who are probably the target group of this book. I'm just an architect/developer/technical leader and for me, there was too much fillers and repetitions and marketing/vision/business stuff & fluff.
Slightly interesting is the technical part, or rather "technical" (still not specific enough for my level), which inspired me to study some interesting tools/technologies, like Swagger, or Docker.
Feel free to suggest some better book about microservices in comments.
April 18, 2017
The book is an excellent introduction about microservices. It's very high level so don't expect implementations or any fine-grained details however, the book reference dozens of other books and videos for further details. The reason i like this book that it introduces lots of new principles and references if you needed more details.
October 5, 2016
Kecy, kecy a zase jen kecy.
May 6, 2019
Una explicación sencilla de microservicios para personas que son novatas o que se están adentrando al mundo de los microservicios. Da muy buenos tips y herramientas, que como menciona el autor, para la fecha en que se lee el libro ya hayan sido reemplazadas. Mi único "pero" es que la metáfora que hace al inicio de la carretera para explicar la rapidez con la seguridad, no se me hace explicativa hasta más adentrado en el libro.
July 30, 2023
Nice summary of microservice architecture principles. Good to structure my knowledge.
I agree with speed and safety of delivery. I also realized that the main idea to make services replaceable, mainly when business requirements change sometimes it is faster to replace a service as it is small, you can even use another technology that better suits the task.
And also it has a list of sources if you want to read more about the topic.
I agree with speed and safety of delivery. I also realized that the main idea to make services replaceable, mainly when business requirements change sometimes it is faster to replace a service as it is small, you can even use another technology that better suits the task.
And also it has a list of sources if you want to read more about the topic.
March 18, 2018
the moment I finished reading this book I realized that I stand at the beginning of a long road.
Microservices way is a journey more than a destination, a philosophy more than a checklist of do's and donts
This book showed me a roadmap for change to most infrastructures I worked with. I am excited to start this journey of transformation starting tomorrow
Microservices way is a journey more than a destination, a philosophy more than a checklist of do's and donts
This book showed me a roadmap for change to most infrastructures I worked with. I am excited to start this journey of transformation starting tomorrow
May 28, 2024
it isn’t very technical. The content is more for a high-level perspective. I think it is a good start or even focused to CTOs to get the big picture of the microservices architecture, the benefits, what can solve, how can be implemented to your company, etc
November 6, 2017
A very brief overview of Microservices. I mean really brief. Best to read if you need a quick assessment of the architecture and you have never heard of it. Not targeted towards developers.
March 28, 2021
Lots of words, very little meat
February 3, 2022
It’s a good entry point for the subject, but it doesn’t delve as deep enough into the technical aspects as I would’ve liked.
April 27, 2022
The technical information is good but a little more lightweight than what I was hoping for. The information on principles and applying them is superb.
January 13, 2017
The book has one or two interesting sections, but overall it is very superficial and badly written.
What I liked:
The book seems to basically be a collection of everything that the authors could think of regarding microservices. It is clear that from a industry perspective the authors have the knowledge, which shines through in some sections. The section that comes to mind is the one on event sourcing and CQRS.
What I did not like:
Content-wise, the book is basically a rehash of existing sources (blogs, presentations and a couple of books). Annoyingly, the authors do not seem to have learned how to cite. Either entire passages or transcripts are copied into the book, or no reference is given for sections that are clearly taken from other sources.
Furthermore, the authors clearly have no background in Distributed Systems, which is made evident by their lack of terminology and dodging actual fundamentals or issues (e.g. managing dependencies in distributed systems (authors' solution: just try to avoid it)). The issue is also notable by the vagueness of the book. The answer to any issue according to the authors is that it depends on the organization of the reader. To illustrate, the authors, comically, refuse to give any definition/characteristics of the 'microservice architecture', even though the book is named that way.
The book itself is badly written. Terms are not defined, inconvenient issues are glossed over. Even after finishing it, I keep wondering who this book has been written for. It is too shallow for programmers, while too technical, lacking proper explanations for non-technical readers.
What I liked:
The book seems to basically be a collection of everything that the authors could think of regarding microservices. It is clear that from a industry perspective the authors have the knowledge, which shines through in some sections. The section that comes to mind is the one on event sourcing and CQRS.
What I did not like:
Content-wise, the book is basically a rehash of existing sources (blogs, presentations and a couple of books). Annoyingly, the authors do not seem to have learned how to cite. Either entire passages or transcripts are copied into the book, or no reference is given for sections that are clearly taken from other sources.
Furthermore, the authors clearly have no background in Distributed Systems, which is made evident by their lack of terminology and dodging actual fundamentals or issues (e.g. managing dependencies in distributed systems (authors' solution: just try to avoid it)). The issue is also notable by the vagueness of the book. The answer to any issue according to the authors is that it depends on the organization of the reader. To illustrate, the authors, comically, refuse to give any definition/characteristics of the 'microservice architecture', even though the book is named that way.
The book itself is badly written. Terms are not defined, inconvenient issues are glossed over. Even after finishing it, I keep wondering who this book has been written for. It is too shallow for programmers, while too technical, lacking proper explanations for non-technical readers.
February 13, 2017
Bueno pero no genial.
Una lectura que vale la pena, tiene conceptos interesantes. Esta enfocado más que nada a grandes organizaciones pero se puede rescatar conceptos que pueden utilizarse en cualquier contexto. No está enfocado en la tecnología o herramientas pero sí menciona brevemente algunas que son imprescindibles.
Una lectura que vale la pena, tiene conceptos interesantes. Esta enfocado más que nada a grandes organizaciones pero se puede rescatar conceptos que pueden utilizarse en cualquier contexto. No está enfocado en la tecnología o herramientas pero sí menciona brevemente algunas que son imprescindibles.
September 22, 2016
I didn't have much of an understanding of what microservices were and after the first three chapters I was just about as clueless as before. It was like describing music to someone deaf. Long explanations and definitions without examples. But as the book progresses you are introduce to something more concrete and the first few chapters fall into place.
This book is especially useful if you can have a major impact on the dev team direction. Otherwise it's good for programmers that find themselves in such an environnement. If you're in neither situation, hey knowledge is power. At least you'll have an opinion when it comes up.
This book is especially useful if you can have a major impact on the dev team direction. Otherwise it's good for programmers that find themselves in such an environnement. If you're in neither situation, hey knowledge is power. At least you'll have an opinion when it comes up.
October 11, 2016
I kept hearing about Microservice so figured I should read up. I assumed it is a service except just smaller. I was not wrong, but there is much bigger and more fundamental advancement to build the system that can adapt to changes faster therefore aligned with business' need to innovate faster and faster. Especially like its goal of modularization and alignment with DevOps movement. This is bringing fundamental changes to how IT shops are being run. For example, I am see a lot of move to rebuild onsite tech teams (that's been decimated over a decade due to offshoring). The book does a good job of explaining the fundamentals in a easy to understand ways for non-technical people.
September 23, 2016
Good high-level overview of why you might want to use a microservice architecture, the goals and principles you should have if you choose to use it, and what kinds of things you'll need to figure out along the way.
October 11, 2016
As a developer I preferred the perspective presented by Sam Newman's book. However, this book gives a great managerial overview of microservices. And for people wondering whether they should/could convert their software system to microservices, chapter 7 makes it worth buying this book.
September 28, 2016
I prefer "Building Microservices" from Sam Newman since there is a lot of overlap and that one covers more ground
February 19, 2018
Good overview of microservices. I only wish it went more in-depth.
April 21, 2019
A good introduction for beginners.
April 11, 2017
I'm disappointed with this book. it's so boring and superficial. If you know nothing about microservices or want some list of another materials you gonna find it useful. But if you know nothing about microservices, why would you read it?
Displaying 1 - 26 of 26 reviews