Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

Stopping Web Services

Freshness Warning
This article is over 13 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.

This discussion has been closed.

Recently Written

A framework for onboarding new employees (May 15)
There’s no single good way to onboard an employee that works for every role. Here's a framework for creating a process that you can adapt to each situation.
TV hosts as a guide for software managers (May 10)
Software managers can learn a lot from journalists or late night TV hosts and how they interview people.
The Improvement Flywheel (Apr 29)
An incredible flywheel for the improvement of a development team. Fix a few things, and everything starts getting better.
Managers and technical ability (Dec 26)
In technical fields, the closer you are to the actual work being done, the closer your skills need to resemble those of the people doing the work.
Dysfunctions of output-oriented software teams (Sep 17)
Whatever you call it, the symptom is that you're measuring your progress by how much you build and deliver instead of measuring success by the amount of customer value you create.
Evaluative and generative product development (Aug 30)
Customers never even talk to the companies that don't fit their needs at all. If the only product ideas you're considering are those that meet the needs of your current customers, then you're only going to find new customers that look exactly like your current customers.
Product Manager Career Ladder (Aug 19)
What are the steps along the product management career path?
Building the Customer-Informed Product (Aug 15)
Strong products aren't composed of a list of features dictated by customers. They are guided by strong visions, and the execution of that vision is the primary focus of product development.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2020 Adam Kalsey.