Posts tagged api
How are APIs & SOA like Chipotle & Taco Bell? Find out at Accenture & Axway API Workshop event in Dallas on Nov 14

Though it seems like a long time ago now that we’ve had our first snow in Boston, it was just two weeks ago at Axway’s “Connections” event in scorching Arizona where I saw Kevin Kohut present Accenture’s API Maturity Model.

Kevin gave a very entertaining and insightful talk where he rounded on the common SOAP/REST debate, saying that “It’s not about REST vs SOAP, but about API-driven vs SOA-driven” (kicking off a discussion on Twitter).

He also talked about what it means to be API First. He explained that “API First” means that:

  1. The API is the contract, and;
  2. APIs are a product

In the world of SOA, it would have been unusual to find a “product owner” for a Web Service. But in the world of APIs, it is valuable to treat APIs like products in themselves, with owners. This advice from Kevin resonated with many of the API practitioners present at Axway Connections.

One of the most memorable parts of Kevin’s talk was about how APIs are like Chipotle while SOA was like Taco Bell. You’ll have to come along to his talk at the API Workshop in Dallas on the morning of Nov 14 to find out how :) . We’ll also be covering API scenarios such as OAuth SSO for Office365 APIs, Google SSO, mobile access via Angular.js, and integration with the SalesForce API.

(Originally posted in slightly different form at

The power to better manage disparate data flows

This is an excerpt from a transcript of The Axway Blog Team’s podcast, “Key takeaways of the ‘Speed to Revenue and Improved Customer Service’ white paper.”

ANNOUNCER: Hello everyone. The Axway Blog Team recently had a chance to catch up with Peter Benesh, Axway’s director of solution marketing for the Financial Services industry, and ask him to share his thoughts on the key takeaways of the IDC Financial Insights white paper titled “Speed to Revenue and Improved Customer Service: How Data Agility Underpins Success for Financial Institutions in the New Digital Economy” by Alex Kwiatkowski. Key Takeaway 4: Advances in API technology create opportunities to leverage new channels on top of existing services and provide better user experiences, increase revenues, and reduce costs. Real-time integration has the power to better manage disparate data flows and deliver tangible benefits.

PETER BENESH: An immediate example that comes to mind is somebody like Fidelity. If you have a Fidelity account… And say you want to do a 401k rollover. Say you want to close out your 401k and pull the money out. Or let’s say you have an investment portfolio. You have a variety of money market funds, maybe some stock index funds. If you want the flexibility to shift that around very easily and quickly… My personal experience working with some situations like that is you have to call Fidelity, or at least put in a request through a portal. It takes a while for them to confirm that they’ve closed the 401k, that you have to wait seven days or something like that before the check actually gets sent to you. I’m sure a lot of that bureaucracy is created to ensure privacy, to ensure accuracy. But if you could have a technology like the API portal and gateway that provides companies like Fidelity the confidence that all of this is happening securely and within policy, but enables the customers to do it themselves in true real time, then that’s obviously going to attract somebody to that type of service much moreso than one that takes a lot longer. It’d be great if I could just log in to Fidelity and, on the fly, move my money from one market fund to another, rollover 401k, pull money out of a 401k, if I need to close it, and have that all just happen instantaneously.

To download the white paper, click here.

To listen to the podcast on YouTube (audio only), click here.