Externally indexed torrent

If you are the original uploader, contact staff to have it moved to your account

Textbook in PDF format

Proven Patterns for Designing Evolvable High-Quality APIs--For Any Domain, Technology, or Platform.
APIs enable breakthrough innovation and digital transformation in organizations and ecosystems of all kinds. To create user-friendly, reliable and well-performing APIs, architects, designers, and developers need expert design guidance. This practical guide cuts through the complexity of API conversations and their message contents, introducing comprehensive guidelines and heuristics for designing APIs sustainably and specifying them clearly, for whatever technologies or platforms you use.
In Patterns for API Design: Simplifying Integration with Loosely Coupled Message Exchanges, five expert architects and developers cover the entire API lifecycle, from launching projects and establishing goals through defining requirements, elaborating designs, planning evolution, and creating useful documentation. They crystallize the collective knowledge of many practitioners into 44 API design patterns, consistently explained with context, pros and cons, conceptual solutions, and concrete examples. To make their pattern language accessible, they present a domain model, a running case study, decision narratives with pattern selection options and criteria, and walkthroughs of real-world projects applying the patterns in two different industries.
The software components involved in these scenarios—large, small, and in-between—talk to others to achieve their individual goals while jointly serving end users. The software engineer’s response to this distribution challenge is application integration via application programming interfaces (APIs). Every integration scenario involves at least two communication parties: API client and API provider. API clients consume the services exposed by API providers. API documentation governs the client-provider interactions.
Just like humans, software components often struggle to understand each other when they communicate it is hard for their designers to decide on an adequate size and structure of message content and agree on the best-suited conversation style. Neither party wants to be too quiet or overly talkative when articulating its needs or responding to requests. Some application integration and API designs work very well the involved parties understand each other and reach their goals. They interoperate effectively and efficiently. Others lack clarity and thereby confuse or stress participants verbose messages and chatty conversations may overload the communication channels, introduce unnecessary technical risk, and cause extra work in development and operations.
Identify and overcome API design challenges with patterns
Size your endpoint types and operations adequately
Design request and response messages and their representations
Refine your message design for quality
Plan to evolve your APIs
Document and communicate your API contracts
Combine patterns to solve real-world problems and make the right tradeoffs
Foundations and Narratives
Application Programming Interface (API) Fundamentals
Lakeside Mutual Case Study
API Decision Narratives
The Patterns
Pattern Language Introduction
Define Endpoint Types and Operations
Design Request and Response Message Representations
Refine Message Design for Quality
Evolve APIs
Document and Communicate API Contracts
Our Patterns in Action (Now and Then)
Real-World Pattern Stories
Appendix A. Endpoint Identification and Pattern Selection Guides
Appendix B. Implementation of the Lakeside Mutual Case
Appendix C. Microservice Domain-Specific Language (MDSL)