More talks in the program:
09:00 - 10:00
Most projects these days expose or consume some kind of JSON based API, usually working in a RESTful manner. So while the combination of JSON as a data transport format and REST as a means of exposing actions on data seems fairly widely adopted, all these APIs are slightly different.
Trivial decisions about implementation details with respect to the exact JSON structure, naming of REST endpoints etc. are repeated over and over with every team coming to different conclusions, resulting in slightly different APIs. Not only does that result in centuries of man-years being wasted in bikeshedding discussions but also is a massive impediment for code reuse across projects.
The JSON API spec is all about making these trivial decisions once so you don’t have to. This talk introduces the spec, explains what it defines and why it does and points out how everyone profits from adopting it.