- Paperback: 280 pages
- Publisher: O'Reilly Media; 1 edition (February 20, 2015)
- Language: English
- ISBN-10: 1491950358
- ISBN-13: 978-1491950357
- Product Dimensions: 7 x 0.6 x 9.2 inches
- Shipping Weight: 1 pounds (View shipping rates and policies)
- Average Customer Review: 163 customer reviews
- Amazon Best Sellers Rank: #16,121 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Building Microservices: Designing Fine-Grained Systems 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
There is a newer edition of this item:
Frequently bought together
Customers who bought this item also bought
From the Publisher
What Are Microservices?
Microservices are small, autonomous services that work together. Let’s break that definition down a bit and consider the characteristics that make microservices different.
The benefits of microservices are many and varied. Many of these benefits can be laid at the door of any distributed system. Microservices, however, tend to achieve these benefits to a greater degree primarily due to how far they take the concepts behind distributed systems and service-oriented architecture.
Key benefits include:
- Technology Heterogeneity
- Ease of Deployment
- Organizational Alignment
- Optimizing for Replaceability.
About the Author
Sam Newman is interested in how different aspects of technology intersect, from development, to ops, to security, usability, and organizational structures. After 20 years in the industry, Sam now runs his own consulting and training company Sam Newman and Associates, focusing in the area of Microservices, Cloud and CI/CD.
Sam has worked with a variety of companies across multiple industries all over the globe, often with one foot in the developer world, and another in the IT operations space. He has written articles, presented at conferences, and sporadically commits to open source projects. Sam is the author of the bestselling Building Microservices from O'Reilly.
Try the Kindle edition and experience these great reading features:
Read reviews that mention
Showing 1-4 of 163 reviews
There was a problem filtering reviews right now. Please try again later.
In my opinion this book should be read by people used to building traditional monolithic applications, using layered architecture and backed by a relational database.
The author (Sam Newman) will talk about distributed systems in general and new challenges introduced by a migration towards this style. Microservices aren't a silver bullet and perhaps you shouldn't event start with building one, monolithic codebases are fine for short or mid term runs, you can iterate fast, and refactoring and re-shuffling is easy. Once you have solid understanding of your business domain then you could start considering the migration to smaller services (the catch here is to identify the time when this is needed, it shouldn't be neither too soon nor too late). Facade design pattern is a good friend for building coarse-grained services (within the monolith) and then splitting them to smaller services.
Continuous delivery changes once you own multiple microservices (and heck, people can actually OWN them now!), and how not to design for future (sharing via database is plain wrong and introduces terrible amounts of coupling). The only thing I wish was different is the title, it looks like it is trying to take advantage of the new buzzword, but to me this seems like second edition of M. Fowler's "Patterns of Enterprise Software Architecture". And that's a must read.
My only negative comments are these:
* The writing up until chapter 4 seemed somewhat dry, then picked up its pace and became more conversational. However, the earlier chapters' topics are important (and used throughout the book), so don't skip them.
* There's some jargon in the text that's unexplained. Most of it I already knew or could puzzle out, but I'm still curious what a "full-fat virtual machine" is. A glossary would have been nice.
* There are a good number of useful references (with and without URLs) that I hope to check out someday. That would be easier if there were a comprehensive list of references at the end.
Note: I'm not a fan of code- or diagram-heavy technical books on reading devices, but if I were doing it again, I'd buy the kindle version.
The book is very verbose in the topics it discusses and sometimes its hard to stay attentive as the author talks about various topics. If the author had given a few real word examples of microservices running in the industry and had done a in-depth analysis of the pros and cons of the choices made while running the services, then I would've been able to gain a better insight. If the hypothetical Music store used in the book would've been developed in depth, with a good coverage of all aspects of running a business, then it could've been more useful too.
It also recommends some other good books, a few of which I've read already.
In conclusion, this book should be just treated as an intro to the topic of building microservices, but will require a lot more investigation and effort on the part of a reader to run a practical microservice in production.