the architect is not convinced
DESCRIPTION
The platformification of business offers immense potential, but much of it is being left untapped. No doubt companies see internal benefits from their own APIs, which they might open up to select external partners. Yet, even in this API-centric world, consuming another party’s API is entered with relative skepticism, especially when that API resides on a critical path. Developers want to use APIs, but software architects need to be convinced. API providers must be able to answer these criticisms in order to gain significant adoption from companies of all sizes: reliability, including uptime and latency; data ownership and privacy; control over how the service operates; and most of all, the architects need to be convinced your company will survive—and that if you fail, they won’t fail with you. Adam DuVander shares tales from the hockey stick of API growth to the trenches of some of today’s best developer-focused companies.TRANSCRIPT
THE ARCHITECT!IS NOT CONVINCED
Adam DuVander @adamd :!!!
NordicAPIs 2014
Your Typical Developer
Claire Thompson
Claire Thompson
Felipe Venâncio
Ray Devlin
Who is the Architect?
How We’ll Convince the Architect
Control
Reliability
Security
Longevity
Infrastructure APIs
Content APIs
Application APIs
CONTROL
Can We Build It?
Tom Hughes-Croucher Em
Yes We Can! But do we need to?
Can We Touch It?
Dave Lawler
Your Biggest Competitors
You C1 C2 C3
Your Biggest Competitors
You C1 C2 C3
C0
Embrace Standards/Conventions
Lucene Query Syntax
(apis OR api) AND nordic
topic:apis AND country:sweden
days:[1 TO 3]
Client Library Abstractions
db.get('collection', 'key')
db.put('collection', 'key', { “data”: “goes here” })
Client Library Abstractions
db.get('collection', 'key')
db.put('collection', 'key', { “data”: “goes here” })
Data Export
Data Export
my data in
my data out
Bulk Downloads
Bulk Downloads
On Premises / Dedicated Option
John McStravick
RELIABILITY
Twitter’s SXSW Downtime
API Survey
What Downtime?
Goals of a Status Page
Be Transparent
Be Helpful
Be Proactive
Provide Status Updates
Show Current API Health
Show Current API Health
Show Current API Health
Show Recent Issues and Downtime
Show Recent Issues and Downtime
SECURITY
Your Systems
Scott Schiller
Eran Sandler
Process for Data Access
Thom
as Guest
Privacy
Share Best Practices
Data Ownership
LONGEVITY
LaptopMag
LaptopMag
API Business Models
John Musser — bit.ly/apibizmodels
33+ Dead GoogleAPIs
@adamd at #nordicapis
“Worrying about API longevity is just another way to ask for more control.”
THE ARCHITECT!CAN BE CONVINCED
and we can do it together
Ray Devlin
Felipe Venâncio
Convincing the Architect Together
Control: Provide as much as is necessary
Reliability: Be transparent, proactive, helpful
Security: Systems, processes, best practices
Longevity: Do your best, fall back to control
Let’s talk about it: @adamd