Over a million developers have joined DZone.

API Infrastructure Provider Panel Discussion at API Strategy Conference

DZone's Guide to

API Infrastructure Provider Panel Discussion at API Strategy Conference

· Integration Zone
Free Resource

Today’s data climate is fast-paced and it’s not slowing down. Here’s why your current integration solution is not enough. Brought to you in partnership with Liaison Technologies.

View the API Infrastructure provider panel discussion recorded at the API Strategy Conference.

API infrastructure often includes a developer portal, API gateway, key management, service level agreement (SLA) management, monetization, and usage analytics.

Many of today’s APIs rely on 3rd party systems, software and services, and on-premise API infrastructure that comes in various flavors. This panel discussion covers these different API infrastructure flavors, and how to choose between them.

Panel participants included Mark O’Neil (@TheMarkONeill) of Vordel, Alistair Farquharson (@afarqu) CTO of SOA Software, Steve Willmott (@njyx) of 3Scale, Chris Haddad(@cobiacomm) of WSO2, Evgeny Popov(@apopov) of APIphany, and Augusto Marietti (@sinzone) of Mashape.  Kin Lane (@kinlane), API Evangelist, moderated the discussion.

If you are interested in learning more, I have published an API Infrastructure Comparison Chart.

Additional Recommended Reading

Policy Management for APIs

API and SOA Convergence

Scale API Infrastructure

What is an API Management Platform

Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.


Published at DZone with permission of Chris Haddad, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}