December 6, 2017
View all 2 Followers
View all 930 Related Articles
Related Articles (930)
This is the third post of a three-part series covering KPIs for APIs, based on John Musser's presentation at the BAPI Conference that took place this month in New York.
What does a tool maker do when his tool breaks? He builds a new tool to patch the broken one. At least that is what David Beckemeyer (Mr Blog) did when his tweeting garage door opener was threatened by the approaching OAuthpocalypse. This date with destiny for all Twitter programmers is the planned June 30th cutoff of basic authentication. At that point all Twitter apps must communicate with the API through OAuth authentication instead of the much less complicated user name/password form of HTTP Authentication. There are many good reasons for this change, which have been repeated endlessly on the Twitter developer forum, but in practice it is a lot of added complexity, more complexity than David wanted to build into his little, simple garage door device.
MuleSoft has announced a number of key updates that were added to its Anypoint Platform for APIs solution in the month of February. The updates are providing key improvements including automatic deployment functionality, improved portal publishing, and an updated RAML console.