Refactoring of REST API
summary
Shows concrete refactoring moves: identify and model assets, split a huge monolithic REST into domain-specific APIs, and replace monstrous flat parameter lists and RPC-over-HTTP with clear resources and hierarchical URLs. Moves shared security, rate-limiting and payload shaping into an API gateway or backend-for-frontend layer. Cites tooling (Apigee, Kong, Cloud Endpoints, Node-based gateways), migration pattern of extract-and-adapt, and real results: per-client façades and a catalog of unified APIs that cut payloads and integration work in deployed projects.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:13Why REST API matters
- 5:26Modern API development
- 9:44Poor API design issues
- 17:17Refactoring API: first steps
- 20:34Domain and resource separation
- 23:10API Gateway and BFF
- 27:40Redesign and system merging
- 31:13API management tools
- 33:43Summary
- 34:50Q&A
related talks
41mREST API refactoring.
46mLet’s have some effective REST!
48mTransforming a monolith to an API platform
46mEvolving Your HTTP APIs: A Multi-Step Approach
42mLet’s Have Some Effective REST!
37mREST, for real!
32mAdopting a Modern API Strategy for Hybrid, Multi-Cloud Architectures
57mGive it a REST - Tips for designing and consuming public API's
