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 services.
Search
Robson de Almeida
December 05, 2014
Technology
2
110
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
51
The MongoDB Quest - a tale of shards replicas and a lot of data
robsondealmeida
0
53
The Queue is dead! Long live the Event!
robsondealmeida
1
110
Startup for Developers: each line matters.
robsondealmeida
0
77
The Lean Startup na Prática
robsondealmeida
0
180
Other Decks in Technology
See All in Technology
EMとして2023年度に頑張ったこと / What we did well in FY2023 as a EM
pauli
1
170
生産性向上チームの紹介
cybozuinsideout
PRO
1
870
競技としてのKaggle、役に立つKaggle
yu4u
3
1.5k
VS CodeでAWSを操作しよう
smt7174
8
1.7k
Kernel MemoryでAzure OpenAI Serviceとお手軽データソース連携
mitsuzono
1
250
Reducing Cross-Zone Egress at Spotify with Custom gRPC Load Balancing Recap
koh_naga
0
210
複雑な構成要素を持つUIとの向き合い方 〜新・支出グラフでの実例〜 / B43 TECH TALK
nakamuuu
0
140
JAWS-UG Bedrock Claude Night
yamahiro
3
610
家族アルバム みてねにおけるGrafana活用術 / Grafana Meetup Japan Vol.1 LT
isaoshimizu
1
750
【NW X Security JAWS#3】L3-4:AWS環境のIPv6移行に向けて知っておきたいこと
shotashiratori
0
260
プラットフォームってつくることより計測することが重要なんじゃないかという話 / Platform Engineering Meetup #8
taishin
1
370
[新卒向け研修資料] テスト文字列に「うんこ」と入れるな(2024年版)
infiniteloop_inc
4
15k
Featured
See All Featured
The Pragmatic Product Professional
lauravandoore
25
5.8k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
14
1.6k
Java REST API Framework Comparison - PWX 2021
mraible
PRO
18
6.9k
The Invisible Side of Design
smashingmag
294
49k
Stop Working from a Prison Cell
hatefulcrawdad
266
19k
Web Components: a chance to create the future
zenorocha
305
41k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
357
22k
What's in a price? How to price your products and services
michaelherold
237
11k
Infographics Made Easy
chrislema
238
18k
How to train your dragon (web standard)
notwaldorf
73
5.2k
Rails Girls Zürich Keynote
gr2m
91
13k
What’s in a name? Adding method to the madness
productmarketing
PRO
16
2.6k
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