Automotive Grade APIs – designing for longevity
summary
Claim: automotive-grade APIs mean designing for 30–40 year longevity, because cars can sit 10 years offline and then hit current services, forcing support for 20–30 API versions over a vehicle lifetime. Practical rules: pick mature stacks (HTTP/TCP, stable formats), keep interfaces minimal, push protocol complexity into server-side implementations so backends can evolve, and adopt a clear compatibility and versioning strategy so old control units remain interoperable. Simplicity and mature standards
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:43Automotive Grade
- 2:48Longevity
- 4:28Picking the right technology
- 5:08SOAP vs XML
- 6:45TCPIP
- 7:12The survivors
- 8:38API is not just about technology
- 9:13Maintaining API versions
- 11:27Simplicity
- 12:27Clarity
- 14:08Conclusions
related talks
33mDesigning Sustainable APIs
52mDesigning and Implementing REST APIs For the Long Haul
53mAPI Standards 2.0
29mAPI-fying the Engine: Replacing Legacy Automotive Protocols with REST and OAuth.
37mThe end of the beginning of APIs
29m10 years of OpenAPI in the Car Industry
21mScaling API Design
16mBuilding Future-Proof API Platforms