I'm writing this from Sydney Airport, having just rounded out our seven-city
Axway API Workshop tour of Australia and New Zealand, and gearing up for the
world's longest commercial flight (Sydney to Dallas).
If there was any doubt that APIs are a global phenomenon, just take a look at
the attendances the Axway API Workshops over the past 10 days. At Wellington
yesterday we had to commandeer a breakout room because of the large audience,
who were treated to Ben Kepes and an API case study from the New Zealand
Customs Service. I watched the excellent presentations from ANZ Bank and
Infosys from the "standing room only" area, seeing many nodding heads and
ipad note-takers in front of me. Here is Peter Jarman from Infosys explaining
"Why an API Gateway":
This tour makes me cast my mind back to last month, when I spoke with Mark
Boyd (an Aussie in Barcelona) about the glob... (more)
Until recently, when I would talk about "APIs", I would qualify it by saying
"Web APIs", in order to distinguish from the older meaning of APIs as more
the tightly-coupled APIs used in Java, C/C++, or even Visual Basic. If you
just said "APIs", until recently, some people may think you mean APIs like
the Windows API (I can remember Charles Petzold's excellent Windows API book
was on my desk back when I was a programmer at an EDI VAN in the 90s).
Recently Kin Lane has posted some good questions about the nature of APIs on
his blog - he begins by explaining:
Just exactly what an API... (more)
An API Portal is one of the key architectural components of an effective API
Management strategy, along with an API Gateway. They work together
hand-in-hand. The API Portal allows developers to self-register and learn
about your API, while the API Gateway is the "sharp edge" of your API
Management solution, applying policies to API traffic in real-time.
Your APIs cannot be a "Field of Dreams" ("if we build it, they will come").
Instead, you must ensure that your API Portal is engaging, and facilitates
developer self-service. This self-service starts right from the get-go, where
Here are two new job postings looking for Axway API Gateway (Vordel) skills,
one in Phoenix and one in New York City:
This position for an Axway API Gateway (Vordel) Technology Lead is located in
Phoenix, ArizonaThis position for an Axway API Gateway (Vordel / Oracle API
Gateway) expert is located in New York City
New York or Phoenix? Take your pick...
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