- Paperback: 146 pages
- Publisher: O'Reilly Media; 1 edition (August 5, 2016)
- Language: English
- ISBN-10: 1491956259
- ISBN-13: 978-1491956250
- Product Dimensions: 7 x 0.3 x 9.2 inches
- Shipping Weight: 15.5 ounces (View shipping rates and policies)
- Average Customer Review: 8 customer reviews
- Amazon Best Sellers Rank: #201,483 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.
Microservice Architecture: Aligning Principles, Practices, and Culture 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
From the Publisher
Who Should Read This Book
You should read this book if you are interested in the architectural, organizational,and cultural changes that are needed to succeed with a microservice architecture. We primarily wrote this book for technology leaders and software architects who want to shift their organizations toward the microservices style of application development. You don’t have to be a CTO or enterprise architect to enjoy this book, but we’ve written our guidance under the assumption that you are able to influence the organizational design, technology platform, and software architecture at your company.
About the Author
Irakli is CTO and co-founder of a New York health-tech startup ReferWell. At any given time he can be found: designing and implementing APIs, discussing distributed systems architecture and expressing opinions about product management. Prior to ReferWell Irakli held leadership roles at API Academy of CA Technologies, and NPR. Irakli is highly involved in the startup community and has spent over a decade in Washington, DC building innovative products for media companies, government and international organizations, while also being an active open-source contributor and advocate. You can connect to Irakli on Twitter at @inadarei.
As the Director of Design at CA’s API Academy, Ronnie Mitra is focused on helping people design better distributed systems. He travels around the world, helping organisations adopt a design-centric approach to interface design and a system-centric approach to application architecture. Mitra is currently writing a book with Irakli Nadareishvili, Matt McLarty and Mike Amundsen on microservices design and architecture.
Matt McLarty (@mattmclartybc) is Vice President of the API Academy at CA Technologies. The API Academy helps companies thrive in the digital economy by providing expert guidance on strategy, architecture and design for APIs.
An internationally known author and lecturer, Mike Amundsen travels throughout the world consulting and speaking on a wide range of topics including distributed network architecture, Web application development, and other subjects.
In his role of Director of Architecture for the API Academy, Amundsen heads up the API Architecture and Design Practice in North America. He is responsible for working with companies to provide insight on how best to capitalize on the myriad opportunities APIs present to both consumers and the enterprise.
Amundsen has authored numerous books and papers on programming over the last 15 years. His most recent book is a collaboration with Leonard Richardson titled "RESTful Web APIs" published in 2013. His 2011 book, "Building Hypermedia APIs with HTML5 and Node", is an oft-cited reference on building adaptable Web applications.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
My main complaint is that at $39.99 list (~$30 on Amazon), there's just not enough content—a mere 146 pages, and those are small pages with a fairly large font. It's as if these (very knowledgeable) authors submitted an extended outline for something that would have made a great but long technical article, and O'Reilly rushed them into turning it into a short book as quickly as possible.
I've been perusing listings for other recent O'Reilly titles on this topic—Susan Fowler's "Production-ready Microservices" has been highly praised, but offers 172 pages for $38 (Amazon price), which is hard to justify for a technical book. If you bought both, you'd have spent ~$68 for ~300 pages of content that doesn't include much in the way of specifics.
O'Reilly used to be the "go to" for concisely-written, clear, good-value books on rapidly-changing technical topics, but if this is what they've become, it's a lot less compelling.
• 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.
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.
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.