API on Steroids
summary
How to harden a REST API for production when more clients start using it and can accidentally overload it. Covers techniques from the speaker’s experience to make a service more resilient and available (e.g., protection against abusive or runaway requests, scalability and availability improvements).
AI-written summary · about
chapters (9)
- 0:00Introduction to API
- 2:49Data materialization
- 6:23Pagination in API
- 14:17Pagination key and offset
- 24:29Pagination summary
- 25:13Sorting in API
- 29:54Delta shipping and data modeling
- 42:59Summary and best practices
- 44:26Conclusion and contact
related talks
28mAPI Productisation - shift RIGHT to Better Product Resilience
18mUsing APIs appropriately
41mAPI = Some REST and HTTP, Right? RIGHT?!
51mAPI Design in Real Life: What You Don't See in Books
20mPotential of API integrations, common traps and advices
54mFive-step plan for securing your APIs
50mAPI Versioning for REST: In Real Life, How Do We Do It?
28mMaximize API Growth: Strategies from Industry Experts
