Design Patterns for Cloud Native Applications: Patterns in Practice Using APIs, Data, Events, and Streams (Grayscale Indian Edition)

The book content is as described. However, the book itself was moderately damaged. In fact, 3 out of 4 O'Reilly books I've order this week were cosmetically damaged.

TL;DR – This is a pretty good book, and I actually liked it. It's just not a *great* book.First off, every pattern in this book is built around microservices. "Cloud Native" just sounds more buzzy.Second, aside from some references to specific hosted services offered by the big 3 cloud providers, none of these patterns really require the cloud (they could all work in any datacenter).That said, the book does cover a good number of architecture patterns that are well suited for microservice-based apps. It also offers a pretty good list of the leading technologies currently available to build such patterns (i.e. leading databases, messaging libraries, etc.) As such, this book will be handy as a catalog to inspire cloud architecture ideas at a high level (similar to looking at a fashion mag for ideas on your next outfit or hair style).My problem with this book is that it falls into the trap of being stuck in the "middle-ground" – it's probably too complicated for many beginners (making countless assumptions about what they already know and glossing over the details rather than explaining more clearly), but is too basic and generic for real pros.The patterns it presents are all offered at a very high level - they include description of how each pattern logically works, when/why you'd use it, and how it could fit in to a larger system. However, the book contains ZERO example code or concrete guidance on any actual implementation whatsoever (in any language or cloud provider).The authors casually refer to many development patterns and approaches (that often are actually quite complicated underlying technologies and executions), on the assumption that the audience will have the experience to know how to implement them – which pros probably will, but beginners may find overwhelming and frustrating. The authors mix and match these complicated technologies at a description level (casually declaring that you can use _this_ library to build _this_ component, and use _that_ protocol to connect it to _that_ component), without ever offering any actual concrete details or examples of what it takes to actually execute and deliver any of it in a concrete way.On the flip side, for the pros who can mostly imagine how they'd implement this and integrate that, there's not a lot to actually *learn* here. In the end, most of these patterns are actually pretty obvious and well known to pros that are already building in the cloud. While it's nice to have them all in one place, there's really very little that's new here and isn't available elsewhere. In fact, I pulled a full star above due to the total lack of citations these authors _should_ have included when presenting patterns that clearly draw from the prior work of other well-known books and authors (like Fowler, Martin, Evans, Kleppmann, etc.).As I said, it's a good book. It's just not a great book.

Really good book on K8 if you already know the basics of k8 and want to take it to the next level.