API design patterns

API Design Patterns lays out a set of design principles for building internal and public-facing APIs. Google API expert JJ Geewax presents patterns that ensure your APIs are consistent, scalable, and flexible. You'll improve the design of the most common APIs, plus discover techniques for tricky edge cases. Precise illustrations, relevant examples, and detailed scenarios make every pattern clear and easy to understand.

Includes index.

7.3 Implementation.

Intro -- inside front cover -- API Design Patterns -- Copyright -- dedication -- contents -- front matter -- foreword -- preface -- acknowledgments -- about this book -- Who should read this book -- How this book is organized: A roadmap -- About the code -- Live book discussion forum -- Other online resources -- about the author -- about the cover illustration -- Part 1 Introduction -- 1 Introduction to APIs -- 1.1 What are web APIs? -- 1.2 Why do APIs matter? -- 1.3 What are resource-oriented APIs? -- 1.4 What makes an API "good"? -- 1.4.1 Operational -- 1.4.2 Expressive -- 1.4.3 Simple

1.4.4 Predictable -- Summary -- 2 Introduction to API design patterns -- 2.1 What are API design patterns? -- 2.2 Why are API design patterns important? -- 2.3 Anatomy of an API design pattern -- 2.3.1 Name and synopsis -- 2.3.2 Motivation -- 2.3.3 Overview -- 2.3.4 Implementation -- 2.3.5 Trade-offs -- 2.4 Case study: Twapi, a Twitter-like API -- 2.4.1 Overview -- 2.4.2 Listing messages -- 2.4.3 Exporting data -- Summary -- Part 2 Design principles -- 3 Naming -- 3.1 Why do names matter? -- 3.2 What makes a name "good"? -- 3.2.1 Expressive -- 3.2.2 Simple -- 3.2.3 Predictable

3.3 Language, gram…