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
How to Design an API
Search
Simon Wood
July 02, 2014
Technology
0
220
How to Design an API
Talk at London API Meetup on 2nd July 2014.
Simon Wood
July 02, 2014
Tweet
Share
More Decks by Simon Wood
See All by Simon Wood
Killing off legacy tech the right way
hpoom
0
120
Tech's Got Talent
hpoom
1
200
Holiday Extras AWS use case
hpoom
0
99
Node.js & Microservices
hpoom
2
250
Javascript: One language to rule them all
hpoom
0
200
APIs are eating the world
hpoom
2
840
Wake up and smell the API
hpoom
1
120
APIs from the Trenches - API Days Mediterranea 2015
hpoom
0
170
APIs from the Trenches - FOWA 2014
hpoom
4
410
Other Decks in Technology
See All in Technology
ユーザーストーリーのレビューを自動化したみたの
bun913
1
290
「手動オペレーションに定評がある」と言われた私が心がけていること / phpcon_odawara2024
blue_goheimochi
1
310
マルチアカウント環境への発見的統制の導入
ch1aki
1
1.3k
A (short) History of AI
harishpillay
0
100
オーナーシップを持つ領域を明確にする
konifar
8
1k
〜小さく始めて大きく育てる〜データ分析基盤の開発から活用まで
kniino
0
1.9k
ここが嬉しいABAC ここが辛いよABAC #再解説+補足編
masahirokawahara
0
180
なぜ NOT A HOTEL が Web3 に取り組むのか - NOT A HOTEL TECH TALK
ynunokawa
0
160
少数チームで挑む: SwiftUI, TCA, KMPを用いた 新規動画配信アプリ 「ABEMA Live」の開発について
tomu28
0
520
コンテナセキュリティの基本と脅威への対策
kyohmizu
3
670
強みを伸ばすキャリアデザイン
yug1224
0
200
キャラクター制御のためのプロンプト術 for LINE Bot
uezo
0
520
Featured
See All Featured
Building a Scalable Design System with Sketch
lauravandoore
455
32k
Navigating Team Friction
lara
177
13k
Pencils Down: Stop Designing & Start Developing
hursman
116
11k
Agile that works and the tools we love
rasmusluckow
323
20k
Design by the Numbers
sachag
274
18k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
13
1.5k
Become a Pro
speakerdeck
PRO
9
4.5k
For a Future-Friendly Web
brad_frost
171
8.9k
From Idea to $5000 a Month in 5 Months
shpigford
377
45k
[RailsConf 2023] Rails as a piece of cake
palkan
22
3.9k
Making Projects Easy
brettharned
107
5.5k
Scaling GitHub
holman
457
140k
Transcript
How to Design a Unified API London API Group -
02/07/14 Wednesday, 2 July 14
Simon Wood @hpoom Holiday Extras Image by Barney Livingston -
Flickr Wednesday, 2 July 14
@hpoom Wednesday, 2 July 14
@hpoom Over 40m visits and 500k bookings in the last
5 years Give £20m revenue to hotels each year Wednesday, 2 July 14
@hpoom Wednesday, 2 July 14
What I am going to cover The Problem Design Solutions
Considerations Technology @hpoom Wednesday, 2 July 14
LET’S TALK ABOUT THE PROBLEM @hpoom Wednesday, 2 July 14
Multiple sources of data @hpoom Wednesday, 2 July 14
@hpoom Wednesday, 2 July 14
Multiple consumers of data @hpoom Wednesday, 2 July 14
Shortbreaks traffic breakdown 18 months @hpoom Wednesday, 2 July 14
@hpoom Wednesday, 2 July 14
De couple @hpoom Wednesday, 2 July 14
Hide legacy @hpoom Wednesday, 2 July 14
Speed! @hpoom Wednesday, 2 July 14
Source: Strangeloop Networks Case Study Amazon 100 milliseconds revenue 1%
Mozilla 2.2 seconds downloads 60m per year @hpoom Wednesday, 2 July 14
Scaleability @hpoom Wednesday, 2 July 14
Be efficient with resource @hpoom Wednesday, 2 July 14
SO WHAT IS THE THE SOLUTION @hpoom Wednesday, 2 July
14
The Design Bit @hpoom Wednesday, 2 July 14
Website Application Layer Legacy Reservation System @hpoom Wednesday, 2 July
14
Website Application Layer & API Legacy Reservation System Affiliates @hpoom
Wednesday, 2 July 14
Website Application Layer & API Legacy Reservation System Affiliates Hotel
System Ticket System @hpoom Wednesday, 2 July 14
Website Application Layer & API Legacy Reservation System Affiliates Hotel
System Ticket System @hpoom Wednesday, 2 July 14
Unified API Website Mobile App Affiliates Smart TV Hotels Tickets
Transport Food Multiple consumers of data Multiple sources of data @hpoom Wednesday, 2 July 14
Proxy @hpoom Wednesday, 2 July 14
Website Application Layer Legacy Reservation System @hpoom Wednesday, 2 July
14
Website Application Layer Unified API Legacy Reservation System New System
Proxy @hpoom Wednesday, 2 July 14
Hierarchical @hpoom Wednesday, 2 July 14
Website Application Layer Unified API Legacy Reservation System New System
@hpoom Wednesday, 2 July 14
Website Application Layer Unified API Product API Content API Price
& Availability Name Star Rating Facilities @hpoom Wednesday, 2 July 14
Website Application Layer Unified API Product API Content API Hotels
Tickets Transport @hpoom Wednesday, 2 July 14
Website Application Layer Unified API Product API Content API Hotels
Tickets Transport Legacy New Affiliate @hpoom Wednesday, 2 July 14
Micro-service architecture Idea by Fred George - http://bit.ly/fred-george @hpoom Wednesday,
2 July 14
Traditional Enterprise Architecture Micro Service Architecture Diagram by James Hughes
- http://bit.ly/micro-service @hpoom Wednesday, 2 July 14
Website Application Layer Unified API Content API @hpoom Wednesday, 2
July 14
Authentication @hpoom Wednesday, 2 July 14
Unified API Website Mobile App Affiliates Smart TV Hotels Tickets
Transport Food Auth @hpoom Wednesday, 2 July 14
Standardise your payloads @hpoom Wednesday, 2 July 14
PUBLIC SERVICE ANNOUNCEMENT @hpoom This is THE correct way to
write numeric dates 2014-07-02 Source XKCD - http://bit.ly/iso-date Wednesday, 2 July 14
Checksum tricks @hpoom MD5 ("Checksum tricks") = 1aef67e94cf84d9c4200e24cbdc9f93d Wednesday, 2
July 14
Cache & async requests @hpoom Wednesday, 2 July 14
Unified API Website Mobile App Affiliates Smart TV Hotels Tickets
Transport Food Async Total request time is only as slow as the slowest provider 1.2s 0.8s 1.1s 0.6s @hpoom Wednesday, 2 July 14
Unified API Website Mobile App Affiliates Smart TV Hotels Tickets
Transport Food Cache Cache Cache Cache Cache If we hit the top cache respond in 0.04s @hpoom Wednesday, 2 July 14
In summary Solutions Unified API Standard Payloads Micro Services Proxy
Cache & Async Hierarchical Problems Multi Data Sources Multi Consumers Decouple Hide Legacy Speed Scaleability @hpoom Wednesday, 2 July 14
SOME CONSIDERATIONS @hpoom Wednesday, 2 July 14
Open & Commercial @hpoom Wednesday, 2 July 14
The right way to rate limit @hpoom Wednesday, 2 July
14
Who needs access? @hpoom Wednesday, 2 July 14
Unlimited pools of talent @hpoom Chris Jason, ESPN - http://bit.ly/espnapi
Wednesday, 2 July 14
Debugging & Logs @hpoom Wednesday, 2 July 14
Our log data in loggly @hpoom Wednesday, 2 July 14
700k unique payloads 3GB JSON logged daily @hpoom Wednesday, 2
July 14
WHAT TECHNOLOGY? @hpoom Wednesday, 2 July 14
We use... @hpoom express web application framework for node Wednesday,
2 July 14
Yesterday’s Standard SOAP XML Today’s Standard REST JSON Keep it
simple! @hpoom Wednesday, 2 July 14
@hpoom Wednesday, 2 July 14
Language does not matter @hpoom Wednesday, 2 July 14
Good docs @hpoom Pusher Blog - http://bit.ly/devapidocs Wednesday, 2 July
14
TAKE AWAYS @hpoom Wednesday, 2 July 14
APIs Mobile Social Cloud @hpoom Diagram by Sam Ramji -
http://bit.ly/biz-apis Wednesday, 2 July 14
Consume your own APIs @hpoom uses to build Source Zach
Holman - http://bit.ly/githubdogfood uses to build Wednesday, 2 July 14
@hpoom “You wouldn't really think that an online bookstore needs
to be an extensible, programmable platform. Would you?” Steve Yegge Source Steve Yegge - http://bit.ly/yegge Wednesday, 2 July 14
is really important don't screw it up APIs Design @hpoom
Wednesday, 2 July 14
Thanks http://bit.ly/unifiedapi @hpoom twitter + github Simon Wood Wednesday, 2
July 14