Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Everything Is Fragile in the World of APIs

DZone's Guide to

Everything Is Fragile in the World of APIs

"Everything is fragile. Everything will break. Everything will change. Everything will eventually go away." In the world of APIs, do you agree?

· Integration Zone
Free Resource

Share, secure, distribute, control, and monetize your APIs with the platform built with performance, time-to-value, and growth in mind. Free 90-day trial of 3Scale by Red Hat

I was working through some thoughts around programming language dependencies, looking through a service I came across called Bundler and found myself thinking about API dependencies (go figure, man I have a problem), and the reliability of the APIs we are building on top of. Anyways, when it comes to the latest trends in programming languages in a production environment, I'm out of the mainstream current, and when I'm in over my head like this I usually turn to my API Evangelist Slack group for answers.

I asked the group for any random thoughts about programming language dependencies vs. API dependencies. There weren't that many thoughts, except a single profound one from the king of making sure everything is 200 OK, John Sheehan (@johnsheehan), who said:

Everything is fragile!

Deep sh*t, and so very true. As I was pondering the weight of these thoughts, I also came across a page within the USGS water service APIs that was dedicated to helping developers craft fault-resistance code. I think we are just getting started in our understanding of just how fragile the web is, making services like Runscope pretty critical, but also makes having this conversation within your API portal, with your API consumers, like USGS is doing, pretty critical as well. I will also selfishly add that we should be talking more about good practices for API providers, as well as API consumers, in industry blogs that speak to the API sector.

If I've learned anything in six years as the API Evangelist, it is: Everything is fragile. Everything will break. Everything will change. Everything will eventually go away. This applies the to the tech, business, and politics of APIs. This can be a bad thing, or a good thing, depending on how we manage the design, deployment, management, and communicating around our API operations. I'm going to continue to look for other examples of what API providers are doing to help their developers deal with API reliability. I am also going to continue to showcase other successful API design, deployment, and management patterns that are helping us stabilize things, and yes that includes hypermedia.

Explore the core elements of owning an API strategy and best practices for effective API programs. Download the API Owner's Manual, brought to you by 3Scale by Red Hat

Topics:
design ,reliability ,api ,dependencies ,fragile

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}