Don't Let The API Hit You On Your Way Out

As I've discussed here and here, there are risks involved with using free services offered by organizations who keep their code -- and your data -- out of your reach.

Google recently announced that they are shutting down support for their SOAP search API in favor of an AJAX-based API.

To translate the geek-speak: Google used to allow people to build applications that would use Google's search features, but return the results outside Google. Now, with the AJAX API, the results are displayed within Google. With this shift, Google has replaced a very useful tool with more limited option.

Admittedly, this is a pretty small shift. And, Google has a very good argument in that they don't have to give anything away for free -- and both of Google's API's are completely free.

But, from the perspective of educators, what would happen if, in the middle of a course, the ability to access your material changed? How would you cope if, for example, your free service changed to a fee-based service? You would be faced with a choice: ante up the cash to finish the term, or lose access to your work.

When you rely on the largesse of a company providing a free service, you assume and hope that their largesse will continue. But, on the chance that the terms of service shift midstream, what's plan B?