What do you think?
Rate this book
Microservices: Flexible Software Architectures
A Microservice-based architecture divides software systems into many small services which can be deployed independently. Every team works on its own Microservices and is thus decoupled from other teams. This allows to easily scale agile processes. The modularization into Microservices protects the system against architecture decay. Consequently, systems based on Microservices stay maintainable in the long term. In addition, legacy systems can be migrated to Microservices without having to change the legacy code. Moreover, Continuous Delivery is easier to implement in Microservice-based systems. The book is translated from German.
Content
Eberhard Wolff's book offers a comprehensive introduction to Microservices. It covers:
Advantages and disadvantages of the Microservice approach
Microservices vs. SOA (Service-oriented Architecture)
The architecture of Microservice-based systems
The architecture of individual Microservices
Impact on project organization, operation, testing and deployment
Nanoservices
The book explains technology-neutral concepts and architectures which can be implemented with various technologies. As an example a concrete Java technology stack is shown with Spring Boot, the Netflix stack and Spring Cloud.
On the basis of many examples and concrete scenarios you will learn how Microservices can be used as effectively as possible. You will also get suggestions how to deepen what you have learned through your own experiments.
Audience
Software developers
Software architects
Technical project managers
Ops and DevOps engineers
Content
Eberhard Wolff's book offers a comprehensive introduction to Microservices. It covers:
Advantages and disadvantages of the Microservice approach
Microservices vs. SOA (Service-oriented Architecture)
The architecture of Microservice-based systems
The architecture of individual Microservices
Impact on project organization, operation, testing and deployment
Nanoservices
The book explains technology-neutral concepts and architectures which can be implemented with various technologies. As an example a concrete Java technology stack is shown with Spring Boot, the Netflix stack and Spring Cloud.
On the basis of many examples and concrete scenarios you will learn how Microservices can be used as effectively as possible. You will also get suggestions how to deepen what you have learned through your own experiments.
Audience
Software developers
Software architects
Technical project managers
Ops and DevOps engineers
340 pages, Paperback
First published January 10, 2016
30 people are currently reading
127 people want to read
About the author
Eberhard Wolff
28 books35 followersEberhard Wolff has 20+ years of experience as an architect and consultant - often on the intersection of business and technology. He is the Head of Architecture at SWAGLab in Germany. As a speaker, he has given talks at international conferences and as an author, he has written more than 100 articles and books e.g. about Microservices and Continuous Delivery. His technological focus is on modern architectures – often involving Cloud, Domain-driven Design, DevOps, or Microservices.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 6 of 6 reviews
April 28, 2016
Essential Reference on Microservice Architecture
Comprehensive book on Microservice architectures. I think the author did a good job in nailing down both the definition and motivation of a microservice. The writing is a bit dry and repetitive with extremely simplistic examples. Formatting and diagramming could be improved in addition to the author's writing style. These are just aesthetic s and should not prevent you from picking up a copy.
Comprehensive book on Microservice architectures. I think the author did a good job in nailing down both the definition and motivation of a microservice. The writing is a bit dry and repetitive with extremely simplistic examples. Formatting and diagramming could be improved in addition to the author's writing style. These are just aesthetic s and should not prevent you from picking up a copy.
September 6, 2019
Theory theory theory... boring
August 3, 2021
A very theoretical book. A pleasant read, but nothing exceptional, really. Technologies and patterns are up to date. It provides an interesting introduction to different topics of microservices, but does not dive into anything specific. Not recommended to technical people, but rather to Product Owners who are interested to get a better understanding the advantages and challenges of microservices over monoliths.
June 15, 2018
I am a novice software-architect and read a few books on the subject in general. Out of necessity from my work, I bought this book to get a deeper insight into Microservices.
The essential substance of this book is valuable, for it covers a lot of information, all the way from theory to reality. For that alone I would give it five stars.
However, there is little connection to other sources and literature. And those in use - like Evans Domain-Driven-Design, is poorly used. Wolff picked a few patterns from Evans book, most likely in the attempt to best illustrate Microservices in a sophisticated fashion, but ended up making Evans patterns look like they would only apply for Microservices. In many places Wolff stresses how Microservices allow teams of developers to work without supervised coordination and independently of other teams, but the truth is if Evans patterns are well applied in any kind of structural / architectural decision, these boons come to bear all the same. So the way Wolff chose to use external resources gains a three, in my opinion.
The thing I'm most aggravated about is the way Wolff structured the book, but this blade has two edges. If you are a reader looking for a book you don't need to read start to end, but rather just pick out one or two chapters / sections and gain as much information about the whole thing as possible from these - this is your book! Five stars that would be!
Me, though, I wanted to get a deep, detailed look into Microservices. This is what the book does not cover. Information is repeated and duplicated many times, most paragraphs are written in a way that obviously assumes the reader hasn't read any of the previous contents. Hence, if you try to read the book from start to end, you can't dig into the essence of its content. The perspective of the text toward the topic circles around Microservices, swimming back and forth between far away and dipping into what-if scenarios, but there is no progress whatsoever, which makes it very hard to follow. Hence, from my personal agenda when reading this book, the structure would get a solid two stars.
Last but not least, there is my very personal opinion about how the book is written in general. I find the book is written poorly in general. Statements aren't sharp to a point; rather any statement Wolff wants to make is brought together with many words and quasi-statements, fluffed up with whatever example seems to have come to his mind at the moment of writing this particular paragraph. Whenever making a point, he doesn't approach a proper conclusion, and begins pointing back at things already said and forth at things not revealed yet - as if narrative thrill was a quality in text-books. Even the graphics of his own design often fail to deliver what he intends to state with them, which is then worked around with a lot of explanation as mentioned above. At this the book fails at the attempt to be understood by people picking out a chapter or two for their particular needs. If they need to read the whole anyway, because hardly a paragraph does not cross-reference to other sections, what's the point of all the repetition and avoidance of progress in the first place?
With that as my personal reasoning, I must say I really dislike the style of this book. As said in the first place, its contents are valuable, Wolff’s experience as an architect shines through nonetheless. However, I would strongly advise him to get a thorough second looked at Evans patterns, and useing them for his next book.
The essential substance of this book is valuable, for it covers a lot of information, all the way from theory to reality. For that alone I would give it five stars.
However, there is little connection to other sources and literature. And those in use - like Evans Domain-Driven-Design, is poorly used. Wolff picked a few patterns from Evans book, most likely in the attempt to best illustrate Microservices in a sophisticated fashion, but ended up making Evans patterns look like they would only apply for Microservices. In many places Wolff stresses how Microservices allow teams of developers to work without supervised coordination and independently of other teams, but the truth is if Evans patterns are well applied in any kind of structural / architectural decision, these boons come to bear all the same. So the way Wolff chose to use external resources gains a three, in my opinion.
The thing I'm most aggravated about is the way Wolff structured the book, but this blade has two edges. If you are a reader looking for a book you don't need to read start to end, but rather just pick out one or two chapters / sections and gain as much information about the whole thing as possible from these - this is your book! Five stars that would be!
Me, though, I wanted to get a deep, detailed look into Microservices. This is what the book does not cover. Information is repeated and duplicated many times, most paragraphs are written in a way that obviously assumes the reader hasn't read any of the previous contents. Hence, if you try to read the book from start to end, you can't dig into the essence of its content. The perspective of the text toward the topic circles around Microservices, swimming back and forth between far away and dipping into what-if scenarios, but there is no progress whatsoever, which makes it very hard to follow. Hence, from my personal agenda when reading this book, the structure would get a solid two stars.
Last but not least, there is my very personal opinion about how the book is written in general. I find the book is written poorly in general. Statements aren't sharp to a point; rather any statement Wolff wants to make is brought together with many words and quasi-statements, fluffed up with whatever example seems to have come to his mind at the moment of writing this particular paragraph. Whenever making a point, he doesn't approach a proper conclusion, and begins pointing back at things already said and forth at things not revealed yet - as if narrative thrill was a quality in text-books. Even the graphics of his own design often fail to deliver what he intends to state with them, which is then worked around with a lot of explanation as mentioned above. At this the book fails at the attempt to be understood by people picking out a chapter or two for their particular needs. If they need to read the whole anyway, because hardly a paragraph does not cross-reference to other sections, what's the point of all the repetition and avoidance of progress in the first place?
With that as my personal reasoning, I must say I really dislike the style of this book. As said in the first place, its contents are valuable, Wolff’s experience as an architect shines through nonetheless. However, I would strongly advise him to get a thorough second looked at Evans patterns, and useing them for his next book.
June 1, 2016
Nice introduction. The book brings you up to speed.
January 3, 2021
3-4/5 Sterne
Displaying 1 - 6 of 6 reviews