SVCC 2013 - Different Styles of API's

9
Different Style APIs for different audiences Mike Borozdin Director, Integration Development @ DocuSign “Not Always So” – Suzuki Roshi

description

Discussion about protocols, data formats, resources and being open to surprises that the market brings when you try to build a business around your API

Transcript of SVCC 2013 - Different Styles of API's

Page 1: SVCC 2013 -  Different Styles of API's

Different Style APIs for different audiences

Mike BorozdinDirector, Integration Development @ DocuSign

“Not Always So” – Suzuki Roshi

Page 2: SVCC 2013 -  Different Styles of API's

So you think you know APIs?

Page 3: SVCC 2013 -  Different Styles of API's

Different Standards

But…..

Page 4: SVCC 2013 -  Different Styles of API's

The Silicon Valley Bubble

Page 5: SVCC 2013 -  Different Styles of API's

Interesting Facts

SOAPREST

Breakdown of Apps going live using DocuSign API in 2013

Page 6: SVCC 2013 -  Different Styles of API's

Stacks

According to StackOverflow:1) C#2) Java3) JavaScript4) PHP5) C++6) Python7) …

TIOBE Index1) C2) Java3) C++4) Objective-C5) PHP6) C#7) Basic8) Python

Page 7: SVCC 2013 -  Different Styles of API's

Things you didn’t think about

• Interoperability (REST)• WS-Security (SOAP)• Transactions (SOAP)

Page 8: SVCC 2013 -  Different Styles of API's

When to compromise

• Data architecture?• Naming conventions?• Protocols?• Client Libraries?

• Calling conventions?• Data types?• Relationships?

Page 9: SVCC 2013 -  Different Styles of API's

Resource vs. Experience