APIs as infrastructure: future-proofing Stripe with versioning • Hacker News Board

Re: APIs as infrastructure: future-proofing Stripe with versioning

#51

Post by mattbrewsbytes » Wed, Aug 16, 2017, 4:02 PM UTC

If the API is transforming requests/responses essentially auto-magically behind the scenes, then how would a client know what version to upgrade to, in order to get new desired features?

Say it is splitting of street into street1 and street2 for an address element. How would I know what version to target to get this feature?

Re: APIs as infrastructure: future-proofing Stripe with versioning

#52

Post by guzik » Wed, Aug 16, 2017, 10:58 PM UTC

Sounds like migration policy on iOS (Core Data)

Re: APIs as infrastructure: future-proofing Stripe with versioning

#53

Post by hobarrera » Thu, Aug 17, 2017, 2:14 AM UTC

_puk wrote: post #23

di wrote: post #13

Github also versions their API via headers, but uses the `Accept` header instead: https://developer.github.com/v3/media/

I'm surprised they don't run into CDN issues. Have run into more than one issue with the vary: Accept being ignored, resulting in everyone getting the result from the first man in regardless of header variance. Especially noticeable when we tried supporting both JSON and XML via the accepts header, with the version in the mime.

I don't think they run their API servers behind a CDN, that's not really a common thing at all.