The API problem

Karlis Zigurs
Oct 15, 2016 · 1 min read

“no API in the strict sense of its meaning — API is the data”

There’s something beautifully simple, alluring and disruptive in the sentence above (the rest of the source is just a run of the mill blog post). Probably a piece of research from late 80s waiting to be rediscovered.

Now, I’m not saying that we should abandon our http verbs, soap envelopes and json schemas, but lately I’ve been feeling increasingly uneasy about the whole rigid API norm out there.

Graph approach is a step in a right direction, but still remains passive. So much traffic wasted by transmitting megabytes of data just so that the business logic on client device can update a profile to set a flag or add a link.

SQL allows to declare operations on data in-place and only report back the outcome. Can the same be achieved for public API endpoints?

Dealing with autonomous API’s will become a thing within 3–5 years.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store