Artwork

Content provided by APIs You Won't Hate, LLC and APIs You Won't Hate. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by APIs You Won't Hate, LLC and APIs You Won't Hate or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Sunsetting your API

44:46
 
Share
 

Manage episode 285638973 series 1942451
Content provided by APIs You Won't Hate, LLC and APIs You Won't Hate. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by APIs You Won't Hate, LLC and APIs You Won't Hate or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Phil, Mike, and Matt get together for a discussion about how to safely sunset an API endpoint with the end goal being deprecation. We take a look at why its important to be overly communicative about it, what an appropriate length of time is from announcement to deprecation and how you can do it in a way that doesn't make your team or external consumers angry. We talk about the HTTP Sunset Header and the potential HTTP Deprecation Header and how those can make the process of knowing when APIs are being deprecated a lot smoother. We also looked at a few popular JS libraries and discuss how they deprecated themselves.

Show Notes
Request.js deprecation notice
Moment.js deprecation notice
IEFT HTTP Sunset Header Field RFC
IEFT HTTP Deprecation Header Draft
Facebook botching a feature deprecation

Sponsor
Interested in sponsoring this podcast to get the word out about your API product to our listeners? Drop us a line at @apisyouwonthate on twitter and lets get it set up!

  continue reading

52 episodes

Artwork

Sunsetting your API

APIs You Won't Hate

139 subscribers

published

iconShare
 
Manage episode 285638973 series 1942451
Content provided by APIs You Won't Hate, LLC and APIs You Won't Hate. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by APIs You Won't Hate, LLC and APIs You Won't Hate or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Phil, Mike, and Matt get together for a discussion about how to safely sunset an API endpoint with the end goal being deprecation. We take a look at why its important to be overly communicative about it, what an appropriate length of time is from announcement to deprecation and how you can do it in a way that doesn't make your team or external consumers angry. We talk about the HTTP Sunset Header and the potential HTTP Deprecation Header and how those can make the process of knowing when APIs are being deprecated a lot smoother. We also looked at a few popular JS libraries and discuss how they deprecated themselves.

Show Notes
Request.js deprecation notice
Moment.js deprecation notice
IEFT HTTP Sunset Header Field RFC
IEFT HTTP Deprecation Header Draft
Facebook botching a feature deprecation

Sponsor
Interested in sponsoring this podcast to get the word out about your API product to our listeners? Drop us a line at @apisyouwonthate on twitter and lets get it set up!

  continue reading

52 episodes

Alle Folgen

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide