16:30-17:00 Phil Sturgeon: API Descriptions as Production Code

API Description Documents (a.k.a “specifications”) can be used for all sorts of time and money saving things. At this point most developers are aware they can help with docs and have maybe played around with mocking, but they often have this concern about “keeping specs in sync with code”.

This talk walks through using API description documents for client-side validation (avoid validation hell by telling your clients how they should handle validation), server-side validation in the application (stop writing complex validation logic in your ORM model or some other awkward place), and validation in the API gateway (don’t even bother wasting application server resources with invalid requests).