API design: Which version of versioning is right for you?

Re:API design: Which version of versioning is right for you? by chrisweekly on Sunday October 06, 2019 @05:51PM (#21175419)

Could you please give an example of these property-based entities, or link to an API that follows this approach? I think I understand your suggestion but want to be sure. New endpoints for new semantics seems rock-solid to me along same lines as content-addressable / immutable build artifacts which I endorse.

[ Parent | on HN ]

Re:API design: Which version of versioning is right for you? by wellpast on Sunday October 06, 2019 @06:04PM (#21175478)

Rich Hickey explains a similar thinking in this talk https://youtu.be/oyLBGkS5ICk but it’s more directed at code libraries. The same arguments apply.

I 100% think this is the way to go for internal APIs.

For public APIs I may change my opinion here for more sociological/political reasons. The rational/technical reasons all still remain.

[ Parent | on HN ]

Re:API design: Which version of versioning is right for you? by chrisweekly on Sunday October 06, 2019 @08:51PM (#21176330)

Thanks! Helpful link, and args simply / well-put. :)

[ Parent | on HN ]