API Digest #23: Politics Behind the Curtain of APIs

Published 10 August 2015 | Updated 18 August 2017 |

Politics Behind the Curtain of APIs

APIs are often looked upon as a chiefly technical term. Where code talk is omitted, politics and business come as the subject matter. As you have probably guessed, API Digest is back with some serious materials reviewed.

Let's stop kidding ourselves about APIs… API is a political concept, not a technical one”, argues Martin Sustrik in his recent article. Feel like reading or writing a comment? Do it by clicking the link.

If you are looking for a place to either find an API or list your own one, Bill Doerrfeld’s post will stand you in good stead. Find the 11 API directories that could be just what you need by following this link.

Daniel Elizalde has sparked another brilliant article for Tech Product Management. Read The Business of APIs: What Product Managers Need to Plan For to discover key benefits and challenges of open APIs as well as why Product Managers should treat an open API as its own product instead of as a feature.

Sam Macklin believes that every company with an API needs an API evangelist. To find the explanations he provides, click here.

Mulesoft CTO Uri Sarid has been interviewed for The Enterprisers Project. Read his answers to find out why CTOs must design for developers right from the start and how to create software that meets needs you can't anticipate.

Do not miss Arnaud Lauret’s exclusive interview for API2Cart. Find out who he would like to be, what his homework dipsy doodles were, and what cardinal virtues every API should follow are.

In case you have missed the latest posts by Kin Lane, here is the cream of them:

We are finishing with microservices. Two presentations on the topic have been added on InfoQ.
  • Microservices Are (Conceptually) Too Big by Phil Wills (he believes that thinking about independent services and single responsibility applications rather than microservices can help to clarify the architectural trade-offs between the complexities of growing one application and those of communicating between many)
  • Microservices: Software that Fits in Your Head by Dan North (the speaker describes a model for thinking about the age of code and argues for replaceability as a first class concern. He also discovers that if one optimizes for both replaceability and consistency he can end up with something that looks a lot like microservices)
Let us know what topics you would like to see covered in API digests. Feel free to make a suggestion by sending us an e-mail.