Real-World Enterprise REST API Design
summary
Argues for using the minimal tooling to produce a maintainable REST surface: structure URLs to allow added resources, design types so schemas can be extended, and avoid over-engineering. Notes microservice migration removes global transactions so APIs need an explicit protocol to sequence operations and preserve eventual consistency across services. Demonstrates a small open‑source project called apicana that wires simple OSS tools together to produce a lightweight API that keeps the system evolvable and keeps the doors open to future changes.
AI-written summary · about
related talks
54mEffective Design of RESTful APIs
42mREST API design good practices
51mREST beyond the obvious – API design for ever evolving systems
24mDesigning the APIs for an Internal Set of Services
42mLet’s Have Some Effective REST!
01h 39mLet’s have some Effective REST
53mEffective Design of RESTful APIs
21mReal-World Enterprise REST API Design