There has been massive adoption of Web APIs, and many stats and commentary exist around API exposure and business models - but what about API integration? This presentation will take a look at the challenges that exist around integration in 2017, looking at data we’ve collected from a large variety of enterprise cloud apps. We’ll look at some of the trends we are seeing among service providers that ease the developer burden and make some recommendations to ensure the APIs we’re building today are fit for purpose tomorrow.
3. #SuccessfulAPIs
@gssor
WHY THIS TOPIC?
Focus on how the growth in APIs has had an
impact on the growing demand for connectivity.
To determine how well APIs are optimized for integration.
4. #SuccessfulAPIs
@gssor
WHY THIS TOPIC?
Focus on how the growth in APIs has had an
impact on the growing demand for integration.
To determine how well APIs are optimized for integration.
connectivity
7. #SuccessfulAPIs
@gssor
METHODOLOGY
DATA COLLECTION
Data collected between September 2016 - March 2017 .
PRIMARY SOURCE: Cloud Elements Platform of APIs
- 165 Public Apps and Services
- 28,000 Integration Instances
- 1.6 Billion API Calls
Complementary Research from:
- SmartBear State of API Report 2016
- Datanyze Market Share Reports of 2016
- ProgrammableWeb API Directory - Growth in Web APIs 2005 - 2016
14. #SuccessfulAPIs
@gssor
Enterprises have over 1,031 internal cloud services. Of
those enterprises, 39% want easier integration between the
tools they already use.
THE BIGGESTCHALLENGES IN API TECHNOLOGY
SMARTBEAR STATE OF API REPORT 2016
https://smartbear.com/resources/ebooks/state-of-api-survey-report-2016/
20. #SuccessfulAPIs
@gssor
“
58% OF ENDPOINTS SUPPORT
SOME METADATA DISCOVERY
One caveat to this research is that it’s
heavily weighted by the custom
integrations provided by Cloud Elements.
It’s natural for us to support cooperative
endpoints.
Our sense that industry-wide, less than
15% of endpoints actually support
discovery.
23. #SuccessfulAPIs
@gssor
HTTP STATUS RANGES:
1xx: Hold Please
2xx: Great Success
3xx: Go Away!
4xx: You Screwed Up
5xx: We Screwed Up
HTTP 299: Disappointed -
The server has accepted your request but
thinks you can do better
26. #SuccessfulAPIs
@gssor
“Enterprise users are often dealing with vast data
lakes that need to be synchronized, analyzed,
migrated, or even shared. Application providers
must think carefully about the functionality they
offer to handle this scale of data.