This document summarizes a presentation aimed at convincing an architect to use APIs. It discusses controlling APIs, reliability through transparency and status updates, securing systems and data access, and ensuring longevity despite inevitable API shutdowns. The conclusion is that providing necessary control, transparency about reliability, strong security practices, and accepting limits to longevity can convince the architect to use APIs, especially by continuing an open dialogue.

1. THE ARCHITECT!
IS NOT CONVINCED
Adam DuVander @adamd :!
!
!
NordicAPIs 2014

2. Your Typical Developer
Claire Thompson

3. Claire Thompson

4. Felipe Venâncio

5. Ray Devlin

6. Who is the Architect?

7. How We’ll Convince the Architect
Control
Reliability
Security
Longevity

8. Infrastructure APIs

9. Content APIs

10. Application APIs

11. CONTROL

12. Can We Build It?
Em Tom Hughes-Croucher
Yes We Can! But do we need to?

13. Can We Touch It?
Dave Lawler

14. Your Biggest Competitors
You C1 C2 C3

15. Your Biggest Competitors
You C1 C2 C3
C0

16. Embrace Standards/Conventions

17. Lucene Query Syntax
(apis OR api) AND nordic
topic:apis AND country:sweden
days:[1 TO 3]

18. Client Library Abstractions
db.get('collection', 'key')
db.put('collection', 'key', { “data”: “goes here” })

19. Client Library Abstractions
db.get('collection', 'key')
db.put('collection', 'key', { “data”: “goes here” })

20. Data Export

21. Data Export
my data in
my data out

22. Bulk Downloads

23. Bulk Downloads

24. On Premises / Dedicated Option
John McStravick

25. RELIABILITY

27. Twitter’s SXSW Downtime

28. API Survey

29. What Downtime?

30. Goals of a Status Page
Be Transparent
Be Helpful
Be Proactive

31. Provide Status Updates

32. Show Current API Health

33. Show Current API Health

34. Show Current API Health

35. Show Recent Issues and Downtime

36. Show Recent Issues and Downtime

38. SECURITY

39. Your Systems
Scott Schiller
Eran Sandler

40. Process for Data Access
Thomas Guest

41. Privacy

42. Share Best Practices

43. Data Ownership

44. LONGEVITY

45. LaptopMag

46. LaptopMag

48. API Business Models
John Musser — bit.ly/apibizmodels

49. 33+ Dead GoogleAPIs

53. “Worrying about API longevity is just another
way to ask for more control.”
@adamd at #nordicapis

54. THE ARCHITECT!
CAN BE CONVINCED
and we can do it together

55. Ray Devlin

56. Felipe Venâncio

57. 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