I’ve read this book three times already. I did love it the first time and I enjoyed reading it once again now, almost two years later. Now, equipped with the experience coming from developing and deploying highly available/scalable applications in the cloud anyway, I see it under a different light. Moreover, having read other titles on the subject during these 20 months, allowed me to better value this one.
Let’s start with the title: the title says these 200 pages are about cloud infrastructure patterns. This isn’t exactly true and could lead someone into believing that he gets something that he will not. If you do expect a problem:solution(s) book to common cloud issues, indeed, you will get disappointed. This title does not get you through cloud design challenges that you might face. It does, instead, give you guidelines, best practices that have proven successful in the development of cloud native applications.
What the author does is to present the very basic concepts that better describe a cloud native application, such as scaling in and out, eventual consistency and asynchronous communication, just to mention a couple. Two years later, and after getting through it three times, I would in fact rename this title into Introduction to cloud native application design.
The topics are accurately described, often supported with real life examples. Through the book, the author illustrates how the different concepts apply to an hypothetic (does it exist?) cloud web application called Page of Photos, hosted on Microsoft Azure.
I don’t remember seeing any schematic representation of the concepts explained, which is a big negative point. Some image appears here and there, but they do not really add any value to the reader.
My thoughts on this book definitely changed over the years: it’s a pretty decent book if you are new to the cloud and wanna get an overall idea of the best practices. It is a good starting point. But if you were already exposed to the cloud and its rules, then this book won’t give you anything.