Stopping Web Services

Freshness Warning
This article is over 11 years old. It's possible that the information you read below isn't current.

Yahoo Photos is going away and Jeremy wonders what they should do about the API.

Reading about the pending closure of the Yahoo! Photos and Yahoo! Auctions (in US, at least) services leads to an interesting question for those of us in the business of providing free APIs to our services.

What’s the right way to decommission a Web Service API?

Clearly we ought to strive to shut things down in such a way that breaks people’s code the least (code that we’ve never seen and can’t influence).

There’s some good suggestions and thoughts in the comments.

This is right up the alley of Versioning Web Services in which I pondered the problems of improving an API while not breaking existing clients.

I’m looking for thoughts on how to version a web services API or really any software that’s delivered as a service. How do you prevent changes from having adverse effects while at the same time providing improvements. Is different API versions at different URLs really best or only way to go?

That post garnered some great comments as well.

This isn’t a new problem—at some point all software has to deal with how to end the support cycle for particular versions. However, with web services the problem is complicated because clients are fixed to the upgrade cycle of the server.

For a data structure or service delivered over the public web to a disparate set of clients, this isn’t possible. I cannot time the upgrade of the server to coincide with an upgrade of the client. In many cases, I don’t even know who the client is. I certainly don’t control them. And even if I knew them all, synchronizing an upgrade would require that I coordinate the upgrade schedules of multiple clients, maintained by multiple people, with varying degrees of interest and need.

max
May 11, 2007 8:19 AM

Stopping has 2 p's.

Adam Kalsey
May 11, 2007 8:41 AM

And you don't use apostrophes when pluralizing a word. That would be "P"s unless you're telling me that something belongs to the P.

Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.

Name:

Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Follow me on Twitter

Best Of

  • The best of 2006 I wrote a lot of drivel in 2006. Here's the things that are less crappy than the rest.
  • Where do the RSS ad startups fit in? Yahoo's RSS advertising service could spell trouble for pure-play RSS advertising services unless they adapt their business model.
  • The importance of being good Starbucks is pulling CD burning stations from their stores. That says something interesting about their brand.
  • Rounded corners in CSS There lots of ways to create rounded corners with CSS, but they always require lots of complex HTML and CSS. This is simpler.
  • Lock-in is bad T-Mobile thinks they'll get new Hotspot customers with exclusive content and locked-in devices.
  • More of the best »

Recently Read

Get More

Subscribe | Archives

11

Recently

One on One meetings for managers: Frequency and Duration (Nov 28)
How long should your 1:1s be? How often should you run them?
One on One meetings for managers (Nov 26)
A one on one meeting is one of the top ways you can build your managerial leverage
How the Sales organization in a large company slows innovation (Nov 16)
If you have a new innovative product inside a large established company, it can be much harder to reach product market fit than it would be for the same product in a startup.
Networking as an entrepreneur (Oct 23)
Having a network is crazy important. Networking is not.
Stretching your team (Jun 11)
Stretching your team is one of the best ways to improve your output, your team's happiness, and your velocity. But they'll need coaching.
Physical camera shutter for Cisco Spark Board (Jul 6)
A 3d printable design for a camera shutter for a Cisco Spark Board
My Travel Coffee Setup (Jan 20)
What my travel coffee brewing setup looks like, and how you can build your own for under $100.
Turkey Legs (May 30)
Product naming gone awry.

Subscribe to this site's feed.

Elsewhere

Tropo
Voice and communications platforms, including Tropo and Phono. Work.
SacStarts
The Sacramento technology startup community.
Pinewood Freak
Pinewood Derby tips and tricks

Contact

Adam Kalsey

Mobile: 916.600.2497

Email: adam AT kalsey.com

AIM or Skype: akalsey

Resume

PGP Key

©1999-2018 Adam Kalsey.
Content management by Movable Type.