API DESIGN APPROACH WHICH ONE SHOULD I CHOOSE?

ADRIAN GIGANTE

“A REST API Is not enough for Enterprise Integration“

An API design approach brings REST to the enterprise...

...and defines the success ofyour work as a developer

So… which one should I choose?

CONSIDER:

DocumentationCommunity supportLanguage supportVersioningCode reuseSDK generation

“Developers are the worst users”

..but choosing an API approach is not like choosing:

Spring vs Java EE

Python vs Ruby

Old school integrationlanguages

…you are not that stuck!

API DESIGN APPROACH GUIDES

Some good API design real life examples…

Some good API design real life examples…

{Thanks}

A REST API Is Not Enough for Enterprise Mobile App Integrationhttp://blog.dreamfactory.com/a-rest-api-is-not-enough

API Spec Comparison Toolhttp://www.mikestowe.com/2014/12/api-spec-comparison-tool.php

API Transformerhttps://apitransformer.com

API Guide Designhttp://design.apievangelist.com/tools.html

Twilio REST Web Service Interfacehttps://www.twilio.com/docs/api/rest

Stripe API referencehttps://stripe.com/docs/api#intro

REFERENCE