|
|
|
|
LEADER |
00000cam a2200000Mi 4500 |
001 |
OR_on1261368072 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr cnu---unuuu |
008 |
210724s2021 nyua o 001 0 eng d |
010 |
|
|
|a 2021354501
|
040 |
|
|
|a EBLCP
|b eng
|e rda
|c EBLCP
|d N$T
|d OCLCO
|d YDX
|d OCLCF
|d TOH
|d VT2
|d OSU
|d OCLCO
|d UKAHL
|d OCLCO
|d K6U
|d OCLCQ
|d OCLCO
|
015 |
|
|
|a GBC1E1568
|2 bnb
|
016 |
7 |
|
|a 020307099
|2 Uk
|
019 |
|
|
|a 1283076329
|a 1286904565
|a 1290617238
|
020 |
|
|
|a 9781638350330
|q (electronic book)
|
020 |
|
|
|a 1638350337
|q (electronic book)
|
020 |
|
|
|z 9781617295850
|q (paperback)
|
020 |
|
|
|z 161729585X
|q (paperback)
|
029 |
1 |
|
|a AU@
|b 000069849273
|
035 |
|
|
|a (OCoLC)1261368072
|z (OCoLC)1283076329
|z (OCoLC)1286904565
|z (OCoLC)1290617238
|
050 |
|
4 |
|a QA76.76.A63
|b G44 2021
|
082 |
0 |
4 |
|a 006.76
|2 23
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Geewax, J. J.
|q (John J.),
|e author.
|
245 |
1 |
0 |
|a API design patterns /
|c JJ Geewax ; foreword by Jon Skeet.
|
264 |
|
1 |
|a New York :
|b Manning Publications Co. LLC,
|c [2021]
|
264 |
|
4 |
|c ©2021
|
300 |
|
|
|a 1 online resource (xxxiv, 443 pages) :
|b illustrations
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
500 |
|
|
|a Includes index.
|
505 |
0 |
|
|a 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
|
505 |
8 |
|
|a 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
|
505 |
8 |
|
|a 3.3 Language, grammar, and syntax -- 3.3.1 Language -- 3.3.2 Grammar -- 3.3.3 Syntax -- 3.4 Context -- 3.5 Data types and units -- 3.6 Case study: What happens when you choose bad names? -- 3.7 Exercises -- Summary -- 4 Resource scope and hierarchy -- 4.1 What is resource layout? -- 4.1.1 Types of relationships -- 4.1.2 Entity relationship diagrams -- 4.2 Choosing the right relationship -- 4.2.1 Do you need a relationship at all? -- 4.2.2 References or in-line data -- 4.2.3 Hierarchy -- 4.3 Anti-patterns -- 4.3.1 Resources for everything -- 4.3.2 Deep hierarchies -- 4.3.3 In-line everything
|
505 |
8 |
|
|a 4.4 Exercises -- Summary -- 5 Data types and defaults -- 5.1 Introduction to data types -- 5.1.1 Missing vs. null -- 5.2 Booleans -- 5.3 Numbers -- 5.3.1 Bounds -- 5.3.2 Default values -- 5.3.3 Serialization -- 5.4 Strings -- 5.4.1 Bounds -- 5.4.2 Default values -- 5.4.3 Serialization -- 5.5 Enumerations -- 5.6 Lists -- 5.6.1 Atomicity -- 5.6.2 Bounds -- 5.6.3 Default values -- 5.7 Maps -- 5.7.1 Bounds -- 5.7.2 Default values -- 5.8 Exercises -- Summary -- Part 3 Fundamentals -- 6 Resource identification -- 6.1 What is an identifier? -- 6.2 What makes a good identifier? -- 6.2.1 Easy to use
|
505 |
8 |
|
|a 6.2.2 Unique -- 6.2.3 Permanent -- 6.2.4 Fast and easy to generate -- 6.2.5 Unpredictable -- 6.2.6 Readable, shareable, and verifiable -- 6.2.7 Informationally dense -- 6.3 What does a good identifier look like? -- 6.3.1 Data type -- 6.3.2 Character set -- 6.3.3 Identifier format -- 6.3.4 Checksums -- 6.3.5 Resource type -- 6.3.6 Hierarchy and uniqueness scope -- 6.4 Implementation -- 6.4.1 Size -- 6.4.2 Generation -- 6.4.3 Tomb-stoning -- 6.4.4 Checksum -- 6.4.5 Database storage -- 6.5 What about UUIDs? -- 6.6 Exercises -- Summary -- 7 Standard methods -- 7.1 Motivation -- 7.2 Overview
|
500 |
|
|
|a 7.3 Implementation.
|
520 |
|
|
|a 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.
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
650 |
|
0 |
|a Application program interfaces (Computer software)
|
650 |
|
0 |
|a Application software
|x Development.
|
650 |
|
0 |
|a Web services.
|
650 |
|
6 |
|a Interfaces de programmation d'applications.
|
650 |
|
6 |
|a Logiciels d'application
|x Développement.
|
650 |
|
6 |
|a Services Web.
|
650 |
|
7 |
|a APIs (interfaces)
|2 aat
|
650 |
|
7 |
|a Application program interfaces (Computer software)
|2 fast
|
650 |
|
7 |
|a Application software
|x Development
|2 fast
|
650 |
|
7 |
|a Web services
|2 fast
|
700 |
1 |
|
|a Skeet, Jon,
|e writer of foreword.
|
776 |
0 |
8 |
|i Print version:
|a Geewax, J. J.
|t API Design Patterns
|d New York : Manning Publications Co. LLC,c2021
|z 9781617295850
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781617295850/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
938 |
|
|
|a Askews and Holts Library Services
|b ASKH
|n AH39609029
|
938 |
|
|
|a YBP Library Services
|b YANK
|n 302342101
|
938 |
|
|
|a ProQuest Ebook Central
|b EBLB
|n EBL6680162
|
938 |
|
|
|a EBSCOhost
|b EBSC
|n 2962518
|
994 |
|
|
|a 92
|b IZTAP
|