Главная
Study mode:
on
1
Intro
2
Is that really REST?
3
Anatomy of a REST request
4
Anatomy of a REST response
5
API design - where do you start?
6
An API is a contract
7
Versioning an API
8
Extending an API
9
How do we introduce breaking changes?
10
Elegant deprecation
11
BFF - for compatibility and tailoring
12
Using links to construct a user interface
13
Hypermedia UI (consumer/publisher)
14
Caching - 304 Not Modified
15
Last-Modified header (producer)
16
Rate limiting - 429 Too Many Requests
17
Async and REST
18
Mini PUT/POST.../status example
19
Updating FileRequest status
20
Over consuming (consumer)
21
Enumerated values (consumer)
22
Be specific (consumer)
23
Resources
Description:
Explore best practices for designing and consuming public REST APIs in this comprehensive conference talk. Learn about initial API design, extensibility, versioning, async operations, rate limiting, graceful deprecation, and backend for frontend strategies. Discover how to handle microservices behind an API, consume APIs reliably, and cope with changes without rolling out new releases. Gain insights into caching, rate limiting for clients, and dealing with unexpected responses. Examine real-world problems and solutions from Huddle's experience in updating their public API and creating clients for various platforms. Delve into topics such as anatomy of REST requests and responses, API contracts, hypermedia UI, and efficient resource utilization for both API producers and consumers.

Give it a REST - Tips for Designing and Consuming Public APIs

NDC Conferences
Add to list