Data decay and the illusion of the present

2,381 views

Published on

My slides from the "APIs and The Future of Data" session at the API Strategy & Practice conference, October 22-24 in San Francisco.

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,381
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
9
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Data decay and the illusion of the present

  1. 1. Data Decay and the Illusion of the Present Dan Lynn @danklynn
  2. 2. Keeps all your contacts in one place and keeps them automatically up to date. Based in Denver, Colorado CTO & Co-Founder dan@fullcontact.com @danklynn
  3. 3. Let’s talk about time.
  4. 4. The Past
  5. 5. http://wearcam.org/dundas-square/2004sep23/cement.jpg
  6. 6. The Present The Past The Future
  7. 7. Unless you’re a yogi, you probably can’t even perceive the present.
  8. 8. http://applemagazine.com/wp-content/uploads/2012/12/ exc.jpeg
  9. 9. “Traders may have gotten last week’s Fed news 7 milliseconds early“ - Washington Post (September 24, 2013)
  10. 10. Data is always old It’s just a question of how old.
  11. 11. How do APIs keep data fresh?
  12. 12. Polling GET /notifications?since=1382630675166 • Simple • But can lead to complex scheduling • Trades efficient use of resources for fresh data.
  13. 13. “98.5% of polls are wasted” - Zapier
  14. 14. Ping/Pull • XML-RPC • Facebook Realtime updates • Avoids scheduled polling • Consumer must host an endpoint • Moderate latency (3 hops) • Complex
  15. 15. Push • Github service hooks • Content of change is pushed • Payload can be diff or full resource • Consumer must host an endpoint • Lowest latency (1 hop)
  16. 16. We are moving towards a push-based API ecosystem
  17. 17. Flight Delays “Security is abnormally slow.”
  18. 18. Contact Information “Dan Lynn changed his phone number”
  19. 19. Dynamic Subscriptions POST /contacts/123/subscriptions { "url" : "https://.../updates?contactId=123" } 201 Created { "url" : "/contacts/123/subscriptions/a3b"}
  20. 20. Dynamic Subscriptions DELETE /contacts/123/subscriptions/a3b 200 OK
  21. 21. So which model is right for your API?
  22. 22. What’s the cost of acting on wrong data?
  23. 23. $100 per contact If left untreated Source: SiriusDecisions
  24. 24. Low time sensitivity? Polling is fine.
  25. 25. High time sensitivity? Go with push.
  26. 26. APIs are combating information asymmetry.
  27. 27. Thanks! @danklynn See Also: http://xmpp.org/extensions/xep-0060.html https://code.google.com/p/pubsubhubbub/ http://www.resthooks.org/

×