Atjaunināt sīkdatņu piekrišanu

Principles of Web API Design: Delivering Value with APIs and Microservices [Mīkstie vāki]

3.75/5 (98 ratings by Goodreads)
  • Formāts: Paperback / softback, 368 pages, height x width x depth: 234x186x18 mm, weight: 660 g
  • Sērija : Addison-Wesley Signature Series (Vernon)
  • Izdošanas datums: 05-Mar-2022
  • Izdevniecība: Addison Wesley
  • ISBN-10: 0137355637
  • ISBN-13: 9780137355631
Citas grāmatas par šo tēmu:
  • Mīkstie vāki
  • Cena: 46,90 €
  • Grāmatu piegādes laiks ir 3-4 nedēļas, ja grāmata ir uz vietas izdevniecības noliktavā. Ja izdevējam nepieciešams publicēt jaunu tirāžu, grāmatas piegāde var aizkavēties.
  • Daudzums:
  • Ielikt grozā
  • Piegādes laiks - 4-6 nedēļas
  • Pievienot vēlmju sarakstam
Principles of Web API Design: Delivering Value with APIs and MicroservicesPalielināt
  • Formāts: Paperback / softback, 368 pages, height x width x depth: 234x186x18 mm, weight: 660 g
  • Sērija : Addison-Wesley Signature Series (Vernon)
  • Izdošanas datums: 05-Mar-2022
  • Izdevniecība: Addison Wesley
  • ISBN-10: 0137355637
  • ISBN-13: 9780137355631
Citas grāmatas par šo tēmu:
Permanent link: https://www.kriso.lv/db/9780137355631.html
Keywords:
This is a comprehensive, start-to-finish guide to the processes required for effective API design. Unlike other books, it covers the entire lifecycle. Leading API and microservices consultant James Higginbotham shows how API development teams can successfully integrate processes that occur before, during, and after API design, to scale API development far beyond single individuals or small teams. Higginbotham addresses REST in depth while also fully covering RPC and graph-based API design, as well as messaging, streaming, and event-based async APIs. Coverage includes: 

  • The art of API design, and an overview of the API design process
  • Crafting job stories, conducting EventStorming sessions, and modeling API capabilities
  • Designing APIs that can easily evolve
  • Implementing APIs, and moving to microservices
  • Improving API quality through effective testing, documentation, and protection mechanisms
  • Establishing and maturing your API program: leveraging program and data management techniques that scale



Principles of Web API Design is a comprehensive, start-to-finish guide to the processes required for effective API design. Unlike other books, it covers the entire lifecycle. Leading API and microservices consultant James Higginbotham shows how API developers can successfully integrate processes that occur before, during, and after API design, to scale API development far beyond single individuals or small teams. Higginbotham addresses REST in depth while also fully covering RPC and graph-based API design, as well as messaging, streaming, and event-based async APIs. Coverage includes: 

  • The art of API design, and an overview of the API design process
  • Crafting job stories, conducting EventStorming sessions, and modeling API capabilities
  • Designing APIs that can easily evolve
  • Implementing APIs, and moving to microservices
  • Improving API quality through effective testing, documentation, and protection mechanisms
  • Establishing and maturing your API program: leveraging program and data management techniques that scale

Recenzijas

"I've had the good fortune to work alongside and learn from James over the past several years. His varied institutional knowledge, along with his depth of experience and eye for practical application, makes him unique among his peers. I am ecstatic that others now have the opportunity, in this book, to benefit from James's compelling, pragmatic vision for how to make better APIs. Principles of Web API Design surveys the gamut of available techniques and sets forth a prescriptive, easy-to-follow approach. Teams that apply the guidance in this book will create APIs that better resonate with customers, deliver more business value in less time, and require fewer breaking changes. I cannot recommend Principles of Web API Design enough." --Matthew Reinbold, Director of API Ecosystems, Postman

"In modern software development, APIs end up being both the cause of and solution to many of the problems we face. James's process for dissecting, analyzing, and designing APIs from concepts to caching creates a repeatable approach for teams to solve more problems than they create. --D. Keith Casey, Jr., API Problem Solver, CaseySoftware, LLC

"Following James's clear and easy-to-follow guide, in one afternoon I was able to apply his process to current real-world use cases. I now have the practical guidance, techniques, and clear examples to help me take those next vital steps. Recommended reading for anyone connected to and working with APIs." --Joyce Stack, Architect, Elsevier

" Principles of Web API Design uncovers more than principles. In it, you'll learn a process--a method to design APIs." --Arnaud Lauret, API Handyman

"This insightful playbook guides API teams through a structured process that fosters productive collaboration, valuable capability identification, and best-practice contract crafting. James distills years of experience into a pragmatic roadmap for defining and refining API products, and also provides a primer for API security, eventing, resiliency, and microservices alignment. A must-read for architects either new to the API discipline or responsible for onboarding new teams and instituting a structured API definition process." --Chris Haddad, Chief Architect, Karux LLC

Series Editor Foreword xxi
Foreword xxv
Preface xxvii
Acknowledgments xxxi
About the Author xxxiii
Part I Introduction to Web API Design
1(28)
Chapter 1 The Principles of API Design
3(12)
The Elements of Web API Design
4(2)
Business Capabilities
4(1)
Product Thinking
4(1)
Developer Experience
5(1)
API Design Is Communication
6(1)
Reviewing the Principles of Software Design
7(3)
Modularization
8(1)
Encapsulation
8(1)
High Cohesion and Loose Coupling
9(1)
Resource-Based API Design
10(1)
Resources Are Not Data Models
10(1)
Resources Are Not Object or Domain Models
11(1)
Resource-Based APIs Exchange Messages
12(1)
The Principles of Web API Design
13(1)
Summary
14(1)
Chapter 2 Collaborative API Design
15(14)
Why an API Design Process?
15(1)
API Design Process Antipatterns
16(4)
The Leaky Abstraction Antipattern
16(3)
The Next Release Design Fix Antipattern
19(1)
The Heroic Design Effort Antipattern
19(1)
The Unused API Antipattern
20(1)
The API Design-First Approach
20(2)
Remaining Agile with API Design-First
22(1)
The Agile Manifesto Revisited
22(1)
The Agility of API Design-First
23(1)
The Align-Define-Design-Refine Process
23(3)
The Role of DDD in API Design
26(1)
API Design Involves Everyone
26(2)
Applying the Process Effectively
28(1)
Summary
28(1)
Part II Aligning on API Outcomes
29(38)
Chapter 3 Identify Digital Capabilities
31(14)
Ensuring Stakeholder Alignment
32(1)
What Are Digital Capabilities?
33(1)
Focusing on the Jobs to Be Done
34(1)
What Are Job Stories?
35(1)
The Components of a Job Story
36(1)
Writing Job Stories for APIs
37(1)
Method 1 When the Problem Is Known
37(1)
Method 2 When the Desired Outcome Is Known
37(1)
Method 3 When the Digital Capability Has Been Identified
38(1)
Overcoming Job Story Challenges
38(2)
Challenge 1 Job Stories Are Too Detailed
38(1)
Challenge 2 Job Stories Are Feature Centric
39(1)
Challenge 3 Additional User Context Is Needed
40(1)
Techniques for Capturing Job Stories
40(1)
A Real-World API Design Project
41(1)
Job Story Examples
42(1)
Summary
42(3)
Chapter 4 Capture Activities and Steps
45(22)
Extending Job Stories into Activities and Steps
46(3)
Identify the Activities for Each Job Story
47(1)
Decompose Each Activity into Steps
47(1)
What If Requirements Aren't Clear?
48(1)
Using EventStorming for Collaborative Understanding
49(1)
How EventStorming Works
50(8)
Step 1 Identify Business Domain Events
51(1)
Step 2 Create an Event Narrative
51(3)
Step 3 Review the Narrative and Identify Gaps
54(1)
Step 4 Expand Domain Understanding
54(2)
Step 5 Review the Final Narrative
56(2)
The Benefits of EventStorming
58(2)
Who Should Be Involved?
59(1)
Facilitating an EventStorming Session
60(5)
Prepare: Gathering Necessary Supplies
60(2)
Share: Communicating the EventStorming Session
62(1)
Execute: Conducting the EventStorming Session
63(1)
Wrap-up: Capture Activities and Activity Steps
63(1)
Follow-up: Post-Session Recommendations
63(1)
Customizing the Process
64(1)
Summary
65(2)
Part III Defining Candidate APIs
67(32)
Chapter 5 Identifying API Boundaries
69(10)
Avoiding API Boundary Antipatterns
70(2)
The Mega All-in-One API Antipattern
70(1)
The Overloaded API Antipattern
70(1)
The Helper API Antipattern
71(1)
Bounded Contexts, Subdomains, and APIs
72(1)
Finding API Boundaries Using EventStorming
73(1)
Finding API Boundaries through Activities
73(2)
Naming and Scoping APIs
75(3)
Summary
78(1)
Chapter 6 API Modeling
79(20)
What Is API Modeling?
80(1)
The API Profile Structure
81(1)
The API Modeling Process
81(12)
Step 1 Capture API Profile Summary
83(2)
Step 2 Identify the Resources
85(2)
Step 3 Define the Resource Taxonomy
87(1)
Step 4 Add Operation Events
88(3)
Step 5 Expand Operation Details
91(2)
Validating the API Model with Sequence Diagrams
93(2)
Evaluating API Priority and Reuse
95(1)
Summary
96(3)
Part IV Designing APIs
99(88)
Chapter 7 REST-Based API Design
101(36)
What Is a REST-Based API?
102(10)
REST Is Client/Server
104(1)
REST Is Resource-Centric
104(1)
REST Is Message Based
105(1)
REST Supports a Layered System
105(2)
REST Supports Code on Demand
107(1)
Hypermedia Controls
107(4)
When to Choose REST
111(1)
REST API Design Process
112(13)
Step 1 Design Resource URL Paths
112(3)
Step 2 Map API Operations to HTTP Methods
115(1)
Step 3 Assign Response Codes
116(2)
Step 4 Documenting the REST API Design
118(6)
Step 5 Share and Gather Feedback
124(1)
Selecting a Representation Format
125(7)
Resource Serialization
126(1)
Hypermedia Serialization
127(1)
Hypermedia Messaging
128(1)
Semantic Hypermedia Messaging
129(3)
Common REST Design Patterns
132(4)
Create-Read-Update-Delete
132(1)
Extended Resource Lifecycle Support
133(1)
Singleton Resources
134(1)
Background (Queued) Jobs
134(1)
Long-Running Transaction Support in REST
135(1)
Summary
136(1)
Chapter 8 RPC and Query-Based API Design
137(22)
What Is an RPC-Based API?
138(4)
The gRPC Protocol
139(2)
Factors When Considering RPC
141(1)
RPC API Design Process
142(4)
Step 1 Identify RPC Operations
142(1)
Step 2 Detail RPC Operations
142(3)
Step 3 Document the API Design
145(1)
What Is a Query-Based API?
146(4)
Understanding OData
147(2)
Exploring GraphQL
149(1)
Query-Based API Design Process
150(7)
Step 1 Designing Resource and Graph Structures
151(1)
Step 2 Design Query and Mutation Operations
151(3)
Step 3 Document the API Design
154(3)
Summary
157(2)
Chapter 9 Async APIs for Eventing and Streaming
159(28)
The Problem with API Polling
160(1)
Async APIs Create New Possibilities
161(1)
A Review of Messaging Fundamentals
162(9)
Messaging Styles and Locality
164(1)
The Elements of a Message
165(1)
Understanding Messaging Brokers
166(1)
Point-to-Point Message Distribution (Queues)
167(1)
Fanout Message Distribution (Topics)
167(1)
Message Streaming Fundamentals
168(3)
Async API Styles
171(7)
Server Notification Using Webhooks
171(1)
Server Push Using Server-Sent Events
172(2)
Bidirectional Notification via WebSocket
174(2)
gRPC Streaming
176(1)
Selecting an Async API Style
177(1)
Designing Async APIs
178(6)
Command Messages
178(1)
Event Notifications
179(1)
Event-Carried State Transfer Events
180(2)
Event Batching
182(1)
Event Ordering
183(1)
Documenting Async APIs
184(2)
Summary
186(1)
Part V Refining the API Design
187(116)
Chapter 10 From APIs to Microservices
189(24)
What Are Microservices?
190(2)
Microservices Reduce Coordination Costs
192(1)
The Difference between APIs and Microservices
193(1)
Weighing the Complexity of Microservices
193(5)
Self-Service Infrastructure
194(1)
Independent Release Cycles
194(1)
Shift to Single-Team Ownership
194(1)
Organizational Structure and Cultural Impacts
195(1)
Shift in Data Ownership
195(1)
Distributed Data Management and Governance
196(1)
Distributed Systems Challenges
196(1)
Resiliency, Failover, and Distributed Transactions
197(1)
Refactoring and Code Sharing Challenges
197(1)
Synchronous and Asynchronous Microservices
198(3)
Microservice Architecture Styles
201(3)
Direct Service Communication
201(1)
API-Based Orchestration
201(2)
Cell-Based Architecture
203(1)
Right-Sizing Microservices
204(1)
Decomposing APIs into Microservices
204(6)
Step 1 Identify Candidate Microservices
205(1)
Step 2 Add Microservices into API Sequence Diagrams
206(2)
Step 3 Capture Using the Microservice Design Canvas
208(1)
Additional Microservice Design Considerations
208(2)
Considerations When Transitioning to Microservices
210(1)
Summary
211(2)
Chapter 11 Improving the Developer Experience
213(12)
Creating a Mock API Implementation
214(5)
Static API Mocking
215(1)
API Prototype Mocking
216(1)
Readme-Based Mocking
217(2)
Providing Helper Libraries and SDKs
219(2)
Options for Offering Helper Libraries
220(1)
Versioning Helper Libraries
220(1)
Helper Library Documentation and Testing
221(1)
Offering CLIs for APIs
221(3)
Summary
224(1)
Chapter 12 API Testing Strategies
225(8)
Acceptance Testing
226(1)
Automated Security Testing
226(1)
Operational Monitoring
227(1)
API Contract Testing
227(2)
Selecting Tools to Accelerate Testing
229(1)
The Challenges of API Testing
230(1)
Make API Testing Essential
231(1)
Summary
231(2)
Chapter 13 Document the API Design
233(28)
The Importance of API Documentation
234(1)
API Description Formats
234(14)
OpenAPI Specification
235(3)
API Blueprint
238(2)
RAML
240(4)
JSON Schema
244(1)
API Profiles Using ALPS
245(2)
Improving API Discovery Using APIs.json
247(1)
Extending Docs with Code Examples
248(3)
Write Getting Started Code Examples First
249(1)
Expanding Documentation with Workflow Examples
249(2)
Error Case and Production-Ready Examples
251(1)
From Reference Docs to a Developer Portal
251(2)
Increasing API Adoption through Developer Portals
251(1)
Elements of a Great Developer Portal
252(1)
Effective API Documentation
253(3)
Question 1 How Does Your API Solve My Problems?
254(1)
Question 2 What Problem Does Each API Operation Support?
254(1)
Question 3 How Do I Get Started Using the API?
254(1)
The Role of Technical Writer in API Docs
255(1)
The Minimum Viable Portal
256(3)
Phase 1 Minimum Viable Portal
256(1)
Phase 2 Improvement
257(1)
Phase 3 Focusing on Growth
258(1)
Tools and Frameworks for Developer Portals
259(1)
Summary
260(1)
Chapter 14 Designing for Change
261(12)
The Impact of Change on Existing APIs
261(3)
Perform an API Design Gap Analysis
262(1)
Determine What Is Best for API Consumers
262(1)
Strategies for Change
263(1)
Change Management Is Built on Trust
264(1)
API Versioning Strategies
264(4)
Common Nonbreaking Changes
265(1)
Incompatible Changes
265(1)
API Versions and Revisions
266(1)
API Versioning Methods
267(1)
Business Considerations of API Versioning
268(1)
Deprecating APIs
268(2)
Establish a Deprecation Policy
269(1)
Announcing a Deprecation
269(1)
Establishing an API Stability Contract
270(1)
Summary
271(2)
Chapter 15 Protecting APIs
273(20)
The Potential for API Mischief
273(1)
Essential API Protection Practices
274(2)
Components of API Protection
276(3)
API Gateways
276(1)
API Management
276(1)
Service Meshes
277(1)
Web Application Firewalls
278(1)
Content Delivery Networks
278(1)
Intelligent API Protection
279(1)
API Gateway Topologies
279(5)
API Management Hosting Options
279(3)
API Network Traffic Considerations
282(1)
Topology 1 API Gateway Direct to API Server
283(1)
Topology 2 API Gateway Routing to Services
283(1)
Topology 3 Multiple API Gateway Instances
283(1)
Identity and Access Management
284(5)
Passwords and API Keys
285(1)
API Tokens
286(1)
Pass-by-Reference versus Pass-by-Value API Tokens
287(1)
OAuth 2.0 and OpenID Connect
288(1)
Considerations before Building an In-House API Gateway
289(2)
Reason 1 API Security Is a Moving Target
290(1)
Reason 2 It Will Take Longer than Expected
290(1)
Reason 3 Expected Performance Takes Time
290(1)
What about Helper Libraries?
291(1)
Summary
291(2)
Chapter 16 Continuing the API Design Journey
293(10)
Establishing an API Style Guide
293(4)
Methods for Encouraging Style Guide Adherence
294(1)
Selecting Style Guide Tone
295(1)
Tips for Getting Started with an API Style Guide
296(1)
Supporting Multiple API Styles
296(1)
Conducting API Design Reviews
297(3)
Start with a Documentation Review
298(1)
Check for Standards and Design Consistency
299(1)
Review Automated Test Coverage
299(1)
Add Try It Out Support
299(1)
Developing a Culture of Reuse
300(1)
The Journey Has Only Begun
301(2)
Appendix: HTTP Primer 303(16)
Index 319
James Higginbotham is a software developer and architect with over 25 years of experience in developing and deploying apps and APIs. He guides enterprises through their digital transformation journey, ensuring alignment between business and technology through product-based thinking to deliver a great customer experience. James engages with teams and organizations to help them align their business, product, and technology strategies into a more composable and modular enterprise platform. James also delivers workshops that help cross-functional teams to apply an API design-first approach using his ADDR process. His industry experience includes banking, commercial insurance, hospitality, travel, and the airline industry where he helped to get an airline off the ground--literally. You can learn more about his latest efforts at https://launchany.com and on Twitter @launchany.