Advanced Versioning #112
Description
Stripe for a while was doing a special approach to what they called evolution which had date versions, but its a technically very impressive solution. what this does is show you that you can attempt evolution the normal way (as described in the API Design Guide) and iiiiiffff you really struggle with a specific change that just cannot be handled with a new resource "Let's call it accounts instead of companies because thats more applicable to current business needs anyway" then you can dig this technical solution out of the box and you still dont need versioning. I like it for that reason, but its overkill for most of us. Standard evolution would be fine for 90% of our APIs. 🙂 (edited)
their approach is basically "Migrations" like Facebook used to do, only instead of emailing you and asking you to enable the migration when ready, you send a newer date and it knows you've made all the appropriate changes.
Anyone agree or disagree with that, write it up as an extension to the existing chapter or wedge it in as an.advanced topic later.