Trends in Web APIs
Ronnie MitraPrincipal API Architect - EMEALayer 7 API Academy
The Layer 7 API Academy
Mission:
To help API Publishers build great APIs
Method:
Conference Presentations
Books, Blogs, Tutorials and Tech Talks
Workshops and Mentoring
Ronnie Mitra Mike Amundsen
API
int printf ( const char * format, ... );
Web API
Web API=
Technology
REST/JSON? Yes.SOAP/XML? Yes.HTTP/CSV? Yes.
Is it a Web API?
Design APIs for your users.
Developer experience is Paramount.
API
Today
Tomorrow
The Future
Today
Modern Timeline of Web APIs
2000
Salesforce APIebay API
2002
Amazon API
2004
Flickr API2006
Twitter APIFacebook APIGoogle (Maps) API
2012
Programmableweb.com has 7144 registered APIsSources: apievangelist.com
programmableweb.cominternetarchive.com
Steve Yegge Rantoreilly.com
2005
ebay makes APIs free
2004
First Web 2.0 Conference
2010
Salesforce adds HTTP API
2008
Programmableweb.com has 1000 registered APIs
2005
Programmableweb.com launched54 APIs registered.
The enterprise model:Start with private APIs…
…consider going public in the future
Mobile is driving API publishers
£££Bandwidth is a key constraint
{JSON} SOAP
HTTP-CRUD is the style of choice.
GETPUT
POSTDELETE
/apple/apples/apples?colour=green/bushel/apples/
Designers care about URI design
Security remains importantAPI standards have emerged
OAuth 2 is gaining popularity
SAML
WS-*
Flexibility is the new challenge
LDAP
PKI
API publishers are becoming API consumers
The primary API management challenge:
BalancingControl and Accessibility
API publishers want to encourageutilization
Low barriers to accessSelf serviceSelf documenting
But, API publishers also want to restrict access to APIs
Smart rate limitingSecurity enforcementBrand control
Architects want API gateways
Gateway
API
API
InternalExternal
Developers demand API portals
Portal
Tomorrow
websockets for bi-directional communication
Adaptive APIs – different strokes…
API
The SSO saga will continue…
OpenID Connect will allow apps to retrieve end userInformation – with permission.
User
Bring Your Own Device (BYOD)will drive a new generation of
internal APIs
BYOD
The battle for the definition of RESTwill continue...
Is this REST?
Or is this REST?
HTTP Verbs
URIs
?
Terminology is important…
..but, focusing on design willimprove your API.
The hypermedia feature will become increasingly popular
A
B
Links will become a common facet ofWeb APIs
<bushel><apple id=“23”/>
</bushel>
http://bushel/apple/23
<bushel><link href=“http://bushel/apple/23”>
</bushel>
http://bushel/apple/23
The Future
The hypermedia style will grow…
Templates for input
Task based interaction
Registered content types
Standards and conventions will help us build generic APIs.
Smarter clients will call APIs they didn’t even know existed.
B
Smart
API
Client
A
…but new attack surfaces will lead tonew exploits targeted at APIs
• Mobile Consumers• Secure APIs• Internal and External APIs
• Adaptive APIs• WebSockets and Open ID• Links in APIs
• Smarter Clients• Smarter attacks
Design long lasting APIs
with your users in mind.
Trends in Web APIs
Ronnie MitraPrincipal API Architect - EMEALayer 7 API Academy
Top Related