Crafting Elegant APIs with Laravel
summary
Argues for designing APIs before coding and shows concrete results: API list/detail use Laravel resource classes and route model binding, endpoints get protected by middleware tokens and optionally Laravel Sanctum, specification is validated against OpenAPI with unit tests and a validator package, client caching uses eTag caching, real-world work reduces a page stack from 80 seconds to 200–300 ms, server cache hit rates drop below 1% so BFF layers and URL versioning (v1/v2) handle breaking changes.
AI-written summary · about
chapters (6)
- 0:00API design with Laravel
- 3:33API design considerations
- 11:18Securing API endpoints
- 16:17Live Laravel API demo
- 27:18Verifying APIs post-deployment
- 31:08Q&A
related talks
31mBuilding world-class APIs with API Platform for Laravel
40mEngineering Complex Applications with Laravel 4
54mDocumenting Laravel APIs
01h 07mDesign and Build Great Web APIs
30mDocumenting Laravel APIs
25mWriting resilient code
29mLuke Downing :: Lessons from the Laravel Framework
18mRESTful API: What's New in Laravel 5.5