Great video on API versioning and the [Deprecated] attribute! Quick question: when should old API versions be removed? There isn’t a clear standard. We currently notify consumers manually, but it’s not scalable. I’m thinking of automating this: if a client uses deprecated code, they get a header warning. The frontend could then send an email notification, guiding users to the new version on Swagger. What do you think of this approach, or do you have better suggestions?
Thank you Adrien. Usually old API versions would be removed after three stages: Stage 0/ Update your software to log warnings that API endpoint is about to be deprecated Stage 1/ Communicate to customers directly and indicate a deadline (usually a year or so) that an endpoint is going away Stage 2/ Monitor the traffic on the API endpoint and determine whether it's a good time to shutdown the API On reddit I was having this discussion with someone and I thought, what if we developed api/announcements endpoint that programmatically communicates warnings and deprecations and all that? It needs a good agreed upon data structure that I don't know what it is yet - but it's still an idea. Something to think about.
![[Live สด] การออกรางวัลสลากกินแบ่งรัฐบาล งวดวันที่ 16 พฤศจิกายน 2567](http://i.ytimg.com/vi/wPd7VFfWHIA/mqdefault.jpg)
This is such a unique video. I’ve never seen anything like it on TH-cam. Thank you for sharing and teaching something new!
Your content is always great Hassan.
Great video on API versioning and the [Deprecated] attribute! Quick question: when should old API versions be removed? There isn’t a clear standard. We currently notify consumers manually, but it’s not scalable.
I’m thinking of automating this: if a client uses deprecated code, they get a header warning. The frontend could then send an email notification, guiding users to the new version on Swagger. What do you think of this approach, or do you have better suggestions?
Thank you Adrien.
Usually old API versions would be removed after three stages:
Stage 0/ Update your software to log warnings that API endpoint is about to be deprecated
Stage 1/ Communicate to customers directly and indicate a deadline (usually a year or so) that an endpoint is going away
Stage 2/ Monitor the traffic on the API endpoint and determine whether it's a good time to shutdown the API
On reddit I was having this discussion with someone and I thought, what if we developed api/announcements endpoint that programmatically communicates warnings and deprecations and all that? It needs a good agreed upon data structure that I don't know what it is yet - but it's still an idea. Something to think about.