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
CAPE - Create Anywhere, Publish Everywhere
Search
API Strategy & Practice Conference
April 10, 2013
Technology
1
320
CAPE - Create Anywhere, Publish Everywhere
by Irakli Nadareishvili @ Apistrat NYC (Feb. 2013)
API Strategy & Practice Conference
April 10, 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
280
APIStrat 2016 | OpenAPI Trek: Beyond API Documentation (Arnaud Lauret)
apistrat
5
220
APIStrat 2016 | Flying Dreams: Real-Time Communication from the Edge of Space (Jonathan Barton, Neha Abrol)
apistrat
1
120
APIStrat 2016 | On-prem support? That was so 1982 (Charlie Ozinga)
apistrat
0
99
APIStrat 2016 | Effortless microservices in production with Kubernetes (Ken Wronkiewicz)
apistrat
0
130
Song by Tony Blank
apistrat
0
150
API Lifecycle Manager by Steve Fonseca
apistrat
2
220
APIs In The Enterprise: How Walgreens Formed It's Digital Business by Drew Schweinfurth
apistrat
1
360
Developers Are Difficult by Andrew Noonan
apistrat
0
120
Other Decks in Technology
See All in Technology
社外コミュニティで学び社内に活かす共に学ぶプロジェクトの実践/backlogworld2024
nishiuma
0
270
権威ドキュメントで振り返る2024 #年忘れセキュリティ2024
hirotomotaguchi
2
760
How to be an AWS Community Builder | 君もAWS Community Builderになろう!〜2024 冬 CB募集直前対策編?!〜
coosuke
PRO
2
2.8k
Fanstaの1年を大解剖! 一人SREはどこまでできるのか!?
syossan27
2
170
NilAway による静的解析で「10 億ドル」を節約する #kyotogo / Kyoto Go 56th
ytaka23
3
380
ガバメントクラウドのセキュリティ対策事例について
fujisawaryohei
0
560
開発生産性向上! 育成を「改善」と捉えるエンジニア育成戦略
shoota
2
400
LINE Developersプロダクト(LIFF/LINE Login)におけるフロントエンド開発
lycorptech_jp
PRO
0
120
LINEヤフーのフロントエンド組織・体制の紹介【24年12月】
lycorp_recruit_jp
0
530
【re:Invent 2024 アプデ】 Prompt Routing の紹介
champ
0
150
UI State設計とテスト方針
rmakiyama
2
660
バクラクのドキュメント解析技術と実データにおける課題 / layerx-ccc-winter-2024
shimacos
2
1.1k
Featured
See All Featured
How to Think Like a Performance Engineer
csswizardry
22
1.2k
A Modern Web Designer's Workflow
chriscoyier
693
190k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
356
29k
4 Signs Your Business is Dying
shpigford
181
21k
Producing Creativity
orderedlist
PRO
341
39k
How GitHub (no longer) Works
holman
311
140k
How STYLIGHT went responsive
nonsquared
95
5.2k
Embracing the Ebb and Flow
colly
84
4.5k
The MySQL Ecosystem @ GitHub 2015
samlambert
250
12k
Building Flexible Design Systems
yeseniaperezcruz
327
38k
Building Your Own Lightsaber
phodgson
103
6.1k
Raft: Consensus for Rubyists
vanstee
137
6.7k
Transcript
NPR API Irakli Nadareishvili Director of Engineering, Digital Media, @NPR
Twitter: @inadarei @NPRTechTeam
Create Once, Publish Everywhere • • • • http://bit.ly/capeapi
Today: No Single CMS http://bit.ly/capeapi
http://bit.ly/capeapi
Create Anywhere, Publish Everywhere • • • • • •
• • http://bit.ly/capeapi
Everything Is an API à la Jeff Bezos + Amazon.
Do not create access dualities. All features and content must be accessible through an API. http://bit.ly/capeapi
Speed Is a Feature Faster the API, the more it
gets used. Lowering response time is exponentially hard. http://bit.ly/capeapi
API: Search Index For a distributed publishing system, API is
the content integration point, not: the database of record or federated content. Search engine is a great backend for such APIs. http://bit.ly/capeapi
Granular Security Publishers need control on a single content item
level. Sometimes: even on the level of assets of a content item. http://bit.ly/capeapi
Design for users Forget what they taught you in CS
classes. UML is for Suits. APIs should be designed around real-world queries. http://bit.ly/capeapi
Create Anywhere, Publish Everywhere • • • • • •
• • http://bit.ly/capeapi
http://bit.ly/capeapi