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

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

NDC Conferences via YouTube Direct link

Versioning an API

7 of 23

7 of 23

Versioning an API

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

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

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Is that really REST?
  3. 3 Anatomy of a REST request
  4. 4 Anatomy of a REST response
  5. 5 API design - where do you start?
  6. 6 An API is a contract
  7. 7 Versioning an API
  8. 8 Extending an API
  9. 9 How do we introduce breaking changes?
  10. 10 Elegant deprecation
  11. 11 BFF - for compatibility and tailoring
  12. 12 Using links to construct a user interface
  13. 13 Hypermedia UI (consumer/publisher)
  14. 14 Caching - 304 Not Modified
  15. 15 Last-Modified header (producer)
  16. 16 Rate limiting - 429 Too Many Requests
  17. 17 Async and REST
  18. 18 Updating FileRequest status
  19. 19 Over consuming (consumer)
  20. 20 Enumerated values (consumer)
  21. 21 Relying on link order (consumer)
  22. 22 Be specific (consumer)
  23. 23 Resources

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.