Welcome!

VP Innovation at Axway, Co-founder at Vordel

Mark O'Neill

Subscribe to Mark O'Neill: eMailAlertsEmail Alerts
Get Mark O'Neill via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Mark O'Neill

Here are some predictions for the API space for 2014: Rise of the Client It's generally agreed that an API is only as good as the clients which use it. An unused API is a failure. So that's why it's odd that so much attention has focused on the server side of APIs, with comparatively little attention paid to the client side (there are exceptions though, like Runscope's handy Request Editor and hurl.it, to help developer API clients). If you ask an API provider about how their API is going to be called by clients, often you are met with a hand-wavy answer along the lines of "It's REST, so it's easy". While it may be true that it's easy to hack together a client to call the API that "just works", the problem is that that's all it does. It "just works", but doesn't provide the high-level benefits such as: - Ensuring the API is responding according to your expected service le... (more)

Telstra Hybrid Integration Case Study next week at Gartner AADI Sydney

Next week I'm excited to be attending Gartner AADI Sydney, where the Axway sponsor session features Telstra's Richard King speaking about Hybrid Integration, at 3.15pm on Monday July 21. Hybrid Integration, and the Hybrid Integration Platform (HIP), are very exciting topics in integration at the moment. Connections between on-premises and Cloud services are enabled in this way, all through APIs. Here is the preview of the talk: Innovations in Cloud, Mobile, Social Media and Big Data are revolutionising how Telstra International goes to market to engage with their customers, emplo... (more)

Heartbleed mitigation for Web APIs - Catalog your APIs, and apply a Gateway control point

Gary Oliffe at Gartner has an insightful blog post today about how the Web API angle for Heartbleed has been largely ignored. It reminds me of the DoS attacks on banks this time last year. Everybody seemed to focus on the banking websites which were brought down, but not on the Web APIs which also suffered (and rendered some banking apps unresponsive). People naturally focus on what they can see - websites - not on what they can't see - Web APIs. Gary writes: With all the media coverage of Heartbleed over the last few days it occurred to me that there has not been nearly enough c... (more)

Netflix goes Private: Is this the end of the Public API golden age? And is that a bad thing?

ProgrammableWeb has published a story about how Netflix is taking its API private. In the article, Patricio Robles writes that: "Effective immediately, Netflix has stopped issuing new public API keys to developers and is no longer accepting API affiliates. It is also putting the message boards on its developer portal into read-only mode" http://www.programmableweb.com//news/netflix-closing-public-api-later-year/2014/06/14So what is Netflix doing instead? It is focusing on the known developers who wish to use its APIs. As the ProgrammableWeb article explains, this "small group of kn... (more)

Look Beyond The Mobile or Web Client To The Internet of Things

Kin Lane, the API Evangelist, has produced a list of the Ten API Commandments for Providers. It's a very good list, including privacy, security, and documentation. I encourage everyone to read it and comment. What about the corresponding list for API Consumers? Although I don't want to compare myself to a biblical figure (or indeed to Kin Lane :) ), here is my crack at a list of API commandments for consumers: 1. Protect your API Keys. API Keys are often issued to developers through an API Portal to use in their apps. These API Key allow developers to access apps. Sometimes the key... (more)