Patterns for API Design: Simplifying Integration with Loosely Coupled Message Exchanges (Addison-Wesley Signature Series (Vernon)) 1st Edition

Since I got the book, it has been within reach on my desk and has served as an effective source of knowledge for various API-related questions countless times. The book is thick, no doubt about it, but one should not be discouraged by that fact. Although the book is certainly not intended to be read from cover to cover in one go, it is worth simply opening it up and reading through it. The authors succeed in making the very extensive and substantial content accessible through the following measures:* Introduction and structuring of the content through a domain model * Brief description of a fictional case study that illustrates the theoretical foundations in practice and to which reference is repeatedly made later in the book * Extensive presentation of patterns as a reference work * Structured, graphical representation of the relationships between related or alternative patterns, so that despite the book's large scope, one can efficiently search for help with options and alternatives in architectural decisions. * Very detailed reduction of complex, composite structures to their core components, such as the decomposition of message parameters into their atomic components, before describing how messages can be reduced to their absolute minimum to keep API contracts understandable and maintainable and to make data exchange efficient. In the end, the book goes far beyond the content of a mere reference work, as it even provides an interface description DSL with generative tooling for documenting and implementing API contracts. This clearly demonstrates that the authors did not simply compile existing material, but approached the topic based on deep, long-standing practical experience.

An excellent companion for informed decisions when designing APIs.Chapter 1 starts a bit generic, but then a domain model for remote APIs defines a conceptual frame that is used all over the book.This is a book about software architecture. More than the isolated patterns, chapter 3 describes the decisions behind the application of each one of the patterns. It contains valuable knowledge that drives system design.Then each one of the patterns is neatly described in the second part of the group. But if you have already captured the forces contained in the decisions, you do not need to read them all, but consult them on a need basis.Very clear and concise.

there are useful information but most content were very unnecessary