Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
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? 
Em Tom Hughes-Croucher 
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 
Thomas Guest
Privacy
Share Best Practices
Data Ownership
LONGEVITY
LaptopMag
LaptopMag
API Business Models 
John Musser — bit.ly/apibizmodels
33+ Dead GoogleAPIs
“Worrying about API longevity is just another 
way to ask for more control.” 
@adamd at #nordicapis
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, helpf...
The Architect is Not Convinced
The Architect is Not Convinced
The Architect is Not Convinced
The Architect is Not Convinced
The Architect is Not Convinced
The Architect is Not Convinced
Upcoming SlideShare
Loading in …5
×

The Architect is Not Convinced

765 views

Published on

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.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

The Architect is Not Convinced

  1. 1. THE ARCHITECT! IS NOT CONVINCED Adam DuVander @adamd :! ! ! NordicAPIs 2014
  2. 2. Your Typical Developer Claire Thompson
  3. 3. Claire Thompson
  4. 4. Felipe Venâncio
  5. 5. Ray Devlin
  6. 6. Who is the Architect?
  7. 7. How We’ll Convince the Architect Control Reliability Security Longevity
  8. 8. Infrastructure APIs
  9. 9. Content APIs
  10. 10. Application APIs
  11. 11. CONTROL
  12. 12. Can We Build It? Em Tom Hughes-Croucher Yes We Can! But do we need to?
  13. 13. Can We Touch It? Dave Lawler
  14. 14. Your Biggest Competitors You C1 C2 C3
  15. 15. Your Biggest Competitors You C1 C2 C3 C0
  16. 16. Embrace Standards/Conventions
  17. 17. Lucene Query Syntax (apis OR api) AND nordic topic:apis AND country:sweden days:[1 TO 3]
  18. 18. Client Library Abstractions db.get('collection', 'key') db.put('collection', 'key', { “data”: “goes here” })
  19. 19. Client Library Abstractions db.get('collection', 'key') db.put('collection', 'key', { “data”: “goes here” })
  20. 20. Data Export
  21. 21. Data Export my data in my data out
  22. 22. Bulk Downloads
  23. 23. Bulk Downloads
  24. 24. On Premises / Dedicated Option John McStravick
  25. 25. RELIABILITY
  26. 26. Twitter’s SXSW Downtime
  27. 27. API Survey
  28. 28. What Downtime?
  29. 29. Goals of a Status Page Be Transparent Be Helpful Be Proactive
  30. 30. Provide Status Updates
  31. 31. Show Current API Health
  32. 32. Show Current API Health
  33. 33. Show Current API Health
  34. 34. Show Recent Issues and Downtime
  35. 35. Show Recent Issues and Downtime
  36. 36. SECURITY
  37. 37. Your Systems Scott Schiller Eran Sandler
  38. 38. Process for Data Access Thomas Guest
  39. 39. Privacy
  40. 40. Share Best Practices
  41. 41. Data Ownership
  42. 42. LONGEVITY
  43. 43. LaptopMag
  44. 44. LaptopMag
  45. 45. API Business Models John Musser — bit.ly/apibizmodels
  46. 46. 33+ Dead GoogleAPIs
  47. 47. “Worrying about API longevity is just another way to ask for more control.” @adamd at #nordicapis
  48. 48. THE ARCHITECT! CAN BE CONVINCED and we can do it together
  49. 49. Ray Devlin
  50. 50. Felipe Venâncio
  51. 51. 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

×