About this item:
3.8 out of 5
76.00% of customers are satisfied
5.0 out of 5 stars Comprehensive view of API Architecture
This book shares an architect's view of developing and deploying APIs. They discuss the major components that go into an API architecture and some of the technologies that apply to each one.They use a couple of the architect's tools throughout, specifically C4 diagrams and Architecture Decision Records (ADRs). The ADRs are particularly effective as they evolve the architecture of the example API throughout the chapters.The book is well done and a useful reference.
Easy explained and rich content
This is really good literature in this era of API.
Good book
Has a good breadth of topics and the depth needed for a reference book.
Too high level, too many assumptions
This isn't a bad book. In fact, I enjoyed it. The problem I have is that it's one of those tech books that doesn't address any single audience segment particularly well.For any mid-to-senior level architect or systems/infra engineers, most of what the authors offer in this book is most likely obvious and already well understood. But then, for technical folks who are new to the topics covered, there's hardly any depth - the book moves fast and countless topics get only a passing mention, with some scattered links to references for further reading, etc.The other problem I have with the book is the assumptions the authors make. Further to my above point, they often use tech jargon and refer to trends and technologies with little background, on the assumption you'll know what they're talking about. That's fine for pros – but for a junior reader I anticipate a fair amount of frustration and side-Googling as you read.Finally, one particularly weird assumption they authors make (imho) is that you the reader will be well versed on Kubernetes. A number of the chapters refer to Kubernetes features, operations, architectural details, etc. (not to mention related technologies like Helm, etc.), with zero background introduction on the topic – assuming you the reader are well versed in Kubernetes. I am, so that was fine with me – but nothing in the book title suggests K8s is a prerequisite for large sections of this book. Particularly puzzling, to me, is that almost the only _actually_ _technical_ content in this book (i.e. code/implementation stuff) is YAML config files that are peppered across various chapters relating to configuring various K8s features. ...I would have loved to see a lot more code in this book – but K8s YAML is literally the last thing I had any need for in a book like this. Just... a swing and a miss, if you ask me.Again, overall this is not a bad book. It's simply more of a high-level overview to refresh minds and inspire some thinking than, well… a book that will help anyone _master_ much of anything. :-/
Lacking in any practical detail
Even though the book does give an overview of multiple topics and technologies, it is heavily lacking in detail.
Visit the O'Reilly Media Store
BHD27219
Quantity:
Order today to get by
Free delivery on orders over BHD 20
Product origin: United States
Electrical items shipped from the US are by default considered to be 120v, unless stated otherwise in the product description. Contact Bolo support for voltage information of specific products. A step-up transformer is required to convert from 120v to 240v. All heating electrical items of 120v will be automatically cancelled.
Or share with link
https://bolo.com/