Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Data Decay and the Illusion of the Present
Search
API Strategy & Practice Conference
October 24, 2013
Technology
0
120
Data Decay and the Illusion of the Present
By Dan Lynn @ API Strategy & Practice Conference
San Francisco, October 23-24-25, 2013
API Strategy & Practice Conference
October 24, 2013
Tweet
Share
More Decks by API Strategy & Practice Conference
See All by API Strategy & Practice Conference
APIStrat 2016 | The end of polling: why and how to transform a REST API into a Data Streaming API (Audrey Neveu)
apistrat
12
300
APIStrat 2016 | OpenAPI Trek: Beyond API Documentation (Arnaud Lauret)
apistrat
5
230
APIStrat 2016 | Flying Dreams: Real-Time Communication from the Edge of Space (Jonathan Barton, Neha Abrol)
apistrat
1
140
APIStrat 2016 | On-prem support? That was so 1982 (Charlie Ozinga)
apistrat
0
110
APIStrat 2016 | Effortless microservices in production with Kubernetes (Ken Wronkiewicz)
apistrat
0
160
Song by Tony Blank
apistrat
0
170
API Lifecycle Manager by Steve Fonseca
apistrat
2
240
APIs In The Enterprise: How Walgreens Formed It's Digital Business by Drew Schweinfurth
apistrat
1
370
Developers Are Difficult by Andrew Noonan
apistrat
0
130
Other Decks in Technology
See All in Technology
ラスベガスの歩き方 2025年版(re:Invent 事前勉強会)
junjikoide
0
620
SRE × マネジメントレイヤーが挑戦した組織・会社のオブザーバビリティ改革 ― ビジネス価値と信頼性を両立するリアルな挑戦
coconala_engineer
0
310
AWS DMS で SQL Server を移行してみた/aws-dms-sql-server-migration
emiki
0
260
進化する大規模言語モデル評価: Swallowプロジェクトにおける実践と知見
chokkan
PRO
1
290
SOTA競争から人間を超える画像認識へ
shinya7y
0
640
GPUをつかってベクトル検索を扱う手法のお話し~NVIDIA cuVSとCAGRA~
fshuhe
0
280
データとAIで明らかになる、私たちの課題 ~Snowflake MCP,Salesforce MCPに触れて~ / Data and AI Insights
kaonavi
0
170
20251024_TROCCO/COMETAアップデート紹介といくつかデモもやります!_#p_UG 東京:データ活用が進む組織の作り方
soysoysoyb
0
130
dbtとAIエージェントを組み合わせて見えたデータ調査の新しい形
10xinc
7
1.5k
仕様駆動開発を実現する上流工程におけるAIエージェント活用
sergicalsix
8
4.6k
20251029_Cursor Meetup Tokyo #02_MK_「あなたのAI、私のシェル」 - プロンプトインジェクションによるエージェントのハイジャック
mk0721
PRO
6
2k
ヘンリー会社紹介資料(エンジニア向け) / company deck for engineer
henryofficial
0
430
Featured
See All Featured
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
21
1.2k
Measuring & Analyzing Core Web Vitals
bluesmoon
9
640
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
130k
The World Runs on Bad Software
bkeepers
PRO
72
11k
Done Done
chrislema
185
16k
Into the Great Unknown - MozCon
thekraken
40
2.1k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
16
1.7k
Documentation Writing (for coders)
carmenintech
75
5.1k
Become a Pro
speakerdeck
PRO
29
5.6k
Raft: Consensus for Rubyists
vanstee
140
7.2k
Thoughts on Productivity
jonyablonski
71
4.9k
Building an army of robots
kneath
306
46k
Transcript
Data Decay and the Illusion of the Present Dan Lynn
@danklynn
Keeps all your contacts in one place and keeps them
automatically up to date. Based in Denver, Colorado CTO & Co-Founder
[email protected]
@danklynn
Let’s talk about time.
None
The Past
http://wearcam.org/dundas-square/2004sep23/cement.jpg
The Future The Past The Present
Unless you’re a yogi, you probably can’t even perceive the
present.
http://applemagazine.com/wp-content/uploads/2012/12/ exc.jpeg
- Washington Post (September 24, 2013) “Traders may have gotten
last week’s Fed news 7 milliseconds early“
It’s just a question of how old. Data is always
old
How do APIs keep data fresh?
Polling • Simple • But can lead to complex scheduling
• Trades efficient use of resources for fresh data. GET /notifications?since=1382630675166
- Zapier “98.5% of polls are wasted”
Ping/Pull • XML-RPC • Facebook Realtime updates • Avoids scheduled
polling • Consumer must host an endpoint • Moderate latency (3 hops) • Complex
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)
We are moving towards a push-based API ecosystem
“Security is abnormally slow.” Flight Delays
“Dan Lynn changed his phone number” Contact Information
Dynamic Subscriptions POST /contacts/123/subscriptions { "url" : "https://.../updates?contactId=123" } 201
Created { "url" : "/contacts/123/subscriptions/a3b"}
Dynamic Subscriptions DELETE /contacts/123/subscriptions/a3b 200 OK
So which model is right for your API?
What’s the cost of acting on wrong data?
$100 per contact Source: SiriusDecisions If left untreated
Low time sensitivity? Polling is fine.
High time sensitivity? Go with push.
APIs are combating information asymmetry.
Thanks! @danklynn See Also: http://xmpp.org/extensions/xep-0060.html https://code.google.com/p/pubsubhubbub/ http://www.resthooks.org/