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
R.I.P.: REST in peace! A guide through RESTful ...
Search
Robson de Almeida
December 05, 2014
Technology
2
130
R.I.P.: REST in peace! A guide through RESTful services.
I did this presentation in the #9 Superplayer Hack Sessions.
Robson de Almeida
December 05, 2014
Tweet
Share
More Decks by Robson de Almeida
See All by Robson de Almeida
The Road to Node(JS)
robsondealmeida
0
63
The MongoDB Quest - a tale of shards replicas and a lot of data
robsondealmeida
0
84
The Queue is dead! Long live the Event!
robsondealmeida
1
190
Startup for Developers: each line matters.
robsondealmeida
0
86
The Lean Startup na Prática
robsondealmeida
0
200
Other Decks in Technology
See All in Technology
JAWS AI/ML #30 AI コーディング IDE "Kiro" を触ってみよう
inariku
3
270
【新卒研修資料】数理最適化 / Mathematical Optimization
brainpadpr
25
11k
AI時代の経営、Bet AI Vision #BetAIDay
layerx
PRO
1
1.7k
家族の思い出を形にする 〜 1秒動画の生成を支えるインフラアーキテクチャ
ojima_h
1
340
Mambaで物体検出 完全に理解した
shirarei24
2
210
AI によるドキュメント処理を加速するためのOCR 結果の永続化と再利用戦略
tomoaki25
0
390
データ基盤の管理者からGoogle Cloud全体の管理者になっていた話
zozotech
PRO
0
330
SRE新規立ち上げ! Hubbleインフラのこれまでと展望
katsuya0515
0
160
専門分化が進む分業下でもユーザーが本当に欲しかったものを追求するプロダクトマネジメント/Focus on real user needs despite deep specialization and division of labor
moriyuya
0
1k
Unson OS|48時間で「売れるか」を判定する AI 市場検証プラットフォーム
unson
0
170
2025新卒研修・HTML/CSS #弁護士ドットコム
bengo4com
3
13k
AI関数が早くなったので試してみよう
kumakura
0
120
Featured
See All Featured
The World Runs on Bad Software
bkeepers
PRO
70
11k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
161
15k
Art, The Web, and Tiny UX
lynnandtonic
301
21k
For a Future-Friendly Web
brad_frost
179
9.9k
StorybookのUI Testing Handbookを読んだ
zakiyama
30
6k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
21
1.4k
Producing Creativity
orderedlist
PRO
346
40k
Music & Morning Musume
bryan
46
6.7k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.8k
Being A Developer After 40
akosma
90
590k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
130
19k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
540
Transcript
R.I.P.: REST IN PEACE! a guide through RESTful services
WHY REST ?
WHY REST ? well known concepts optimised technologies and infrastructure
lightweight approach better scale
WHAT REST DO NOT MEANS
WHAT REST DO NOT MEANS REST is NOT a framework
REST is NOT a protocol REST is NOT SOA REST is NOT Client-Server Architecture REST is NOT a URI REST is NOT API
WHAT REST MEANS ?
REST IS ABOUT STYLE
the REST creator
Roy Fielding== Roy Rosello
ROY's WORK … Architectural Styles and the Design of Network-based
Software Architectures REpresentational State Transfer is a architectural style for distributed hypermedia systems HTTP spec & Apache HTTP server
REST CONSTRAINTS
REST CONSTRAINTS CLIENT-SERVER STATELESS RESOURCES
STATELESS each request contains all of the information and cannot
take advantage of any stored context on the server session state is kept entirely on the client
RESOURCES the key abstraction of information in REST is a
resource a resource IS NOT an API or ENDPOINT or METHOD
RESOURCE IDENTIFIER Uniform Resource Identifier (URI) the key to access
the resource { protocol } : { base uri } / { resource path }
URI IS NOT an URL or URN but it covers
it uniform resource locator uniform resource name
REST APIs BEST AND WORSE PRACTICES
NOUNS, NO VERBS
NOUNS, NO VERBS Leave verbs for the HTTP verbs /playlists
/playlists/10 /getAllPlaylists /getPlaylist?id=10 /get?type=playlist&id=10 good bad
HTTP VERBS TO MEAN SOMETHING
GET /playlists GET /playlists/10 POST /playlists PUT /playlists/10 DELETE /playlists/10
HTTP VERBS TO MEAN SOMETHING
HTTP GET SHOULD NOT ALTER THE STATE
use POST, PUT and DELETE. also do not use GET
when you HAVE no choice GET /subscriptions/171/cancel // bad PUT /subscriptions/171/cancel // bad but better ... HTTP GET SHOULD NOT ALTER THE STATE
HTTP STATUS CODE
for successful requests, use 2xx status code. when the client
is wrong, use 4xx status code. for unknown errors, use 5xx status code HTTP STATUS CODE
HTTP HEADERS FOR SERIALIZATION FORMATS
Accept: application/json prefer JSON. HTTP HEADERS FOR SERIALIZATION FORMATS
VERSIONING
prefer /v1, /v2 Instead of /1.0 /v1.0 /20141201 the version
is part of the base URI VERSIONING
ERROR HANDLING
use a standard structure for error messages always identify the
error with a key/code. ERROR HANDLING
THE ZOMBIES FAMILY
THANKS speakerdeck.com/robsondealmeida /robsondealmeida /robsondealmeida