REST in peace @ Osidays 2011 India 11-21-2011

RESTin peace

Bengaluru, 20-22 November 2011

Sorry for the ugly slide.

There will be others.Really sorry.

REST in a nutshell

2000Fielding's dissertation:

REpresentational

Transferhttp://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm

REST in a nutshell:

1. Client <> ServerBengaluru, 20-22 November 2011

REST in a nutshell:

2. Stateless

Servers do not keep anyinformations the clients uses

during different requests.

So the architecture scales well.

3. Cacheable

REST in a nutshell:

Client has access to resources stored betweenit and the origin server.

So communication is faster.

REST in a nutshell:

4. Layered systemBengaluru, 20-22 November 2011

Intermediary nodes can beused along our architecture.

So you efficiently implement point 3.

REST in a nutshell:

5. Uniform interface

Communicate using well-knownverbs and providing all the

informations needed toconsume a service.

So fallbacks are easy.

this was a bit difficult to understand

so, obviously...

nobody had a clue

ANTIPATTERNS

"REST is about

cool URI design"

http://apple.com/users/1/licenses/4.json

"REST is about

cool URI design"

http://apple.com/users/1/licenses/4.json

http://apple.com/site/en_US/showUsers.jsp?uid=1&license=4

is OK too

but, enter simple rule of thumb

cool URIs help youthink in term of resources

- David Zuelke

2URIs (bis)

GET /users POST /users PUT /users/{id} DELETE /users/{id} ...

REST follows a URI schema

GET /users POST /users PUT /users/{id} DELETE /users/{id} ...

REST follows a URI schema

what if you change yourURL?

client is broken

RESTful clients shouldbe driven by service'shypermedia controls

Roy Fielding : http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven

HATEOAS

3POST is cool

said SOAP 1.1

loosing meaningful verbs at the protocol level

nothing cacheable by default

what about bookmarking?

4500 is your friend

said SOAP( again )

GET /users/300Host: www.example.com

HTTP/1.1 500 Internal Server ErrorEtag: 1234X-Powered-By: php/5.3...

The record cannot be found

HTTP/1.1 500 Internal Server ErrorEtag: 1234X-Powered-By: php/5.3...

The record cannot be found

The HTTP protocol is awesome,and lets you return meaningful anduniversally-understood status codes

404 Not Found

OMG Link is broken?

202 Accepted

You get an immediate OK, and the operation will hopefully complete

The WWW

the largest data-exchange network on the planet

And meanwhile, at Facebook...

12TB of new data every day(1 year ago)

500 million users

And meanwhile, at Google...

1 billion unique monthly googlers

via HTTP, baby!

HTTP in a nutshell:

1. Client <> ServerBengaluru, 20-22 November 2011

HTTP in a nutshell:

2. Stateless

http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html

3. widespread cache spec

HTTP in a nutshell:

4. Layered systemOrigin server

Reverse proxy

Great chinese (fire)wall

Company proxy

Lao Tze Song using Firefox 6

HTTP in a nutshell:

5. it is the uniform interfacebetween clients and servers

HTTP bleeds REST

How do Iimplement

thisgoodness?

1. caching & scalability

HTTP cache

Shared/proxy

Shared/reverse proxy

Types of cache

Shared/proxy

Types of cache

Shared/proxy

Types of cache

Shared/proxy

Types of cache

on the server side

Caching withExpiration(example)

HTTP/1.1 200 OKHost: www.example.comExpires: 0

HTTP/1.1 200 OKHost: www.example.comExpires: Tue, 31 Jan 2011 01:00 GMT

HTTP/1.1 200 OKHost: www.example.comCache-Control: max-age=60, public

Cacheable for 60 seconds

Cacheable by both local and shared caches

You can also cache with validation

(Etags, If-None-Match, ...)

Why HTTP cachingis so

important?

Ask yourself:as a developer, what do I want

on my application?

Evolve

Loose coupling

Work less

Evolve Because you want your platform to extensible

Loose coupling

Work less

Loose coupling Because you want it to be easy to integrate with, evolve, plug and mantain

Work less

Loose coupling Because you want it to be easy to integrate with, evolve, plug and mantain

Work less

Because every LoC is bug-prone and our man-day is a hard-to-scale cost

enters our Hero #1

enters our Hero #2

http://www.lullabot.com/articles/a-beginners-guide-to-caching-data

it supportsHTTP caching!

http://drupal.org/node/147310

it supportsHTTP caching!

http://drupal.org/node/147310

( people is supposed to clap their hands here )

wait.... how?

Default headers

Expires = 'Sun, 19 Nov 1978 05:00:00 GMT',

Cache-Control = 'no-cache, must-revalidate',

ETag = $_SERVER['REQUEST_TIME'],

Default headers

is that even legal?

"but you can redefine them!"

drupal_add_http_header()

function drupal_add_http_header(){ ...

drupal_send_headers($headers);}

so, what

drupal_send_headers()

can do so evil?

header(),

of course

which means

drupal_add_http_header('Dumb-Header', 'I\'m batman!');...// other logic...drupal_add_http_header('Dumb-Header', 'I\'m not');

var_dump(headers_list());

drupal_add_http_header('Dumb-Header', 'I\'m batman!');...// other logic...drupal_add_http_header('Dumb-Header', 'I\'m not');

array 0 => string 'X-Powered-By: PHP/5.3.2-1ubuntu4.7' 1 => string 'Dump-Header: I'm not'

drupal_add_http_header('Dumb-Header', 'I\'m batman!');...// other logic...drupal_add_http_header('Dumb-Header', false);

array 0 => string 'X-Powered-By: PHP/5.3.2-1ubuntu4.7' 1 => string 'Dump-Header: I'm batman'

drupal_add_http_header('Dumb-Header', 'I\'m batman!');...// other logic...drupal_add_http_header('Dumb-Header', ' ');

array 0 => string 'X-Powered-By: PHP/5.3.2-1ubuntu4.7' 1 => string 'Dumb-Header:'

you can use header_remove()

( PHP 5.3 )

and create a new class to manage/keep track of

headers and caching directives

but we're lazy

we don't want to reinvent the wheel

Work lessevolve

loose coupling

Work lessevolve

loose coupling

everything is done for us!

but....

tmp files, cache tables, procedural code...

mmmmh....

gotta be something better

Frameworks

Cache is used for compiling routes, autoloading, ...

...but also for storing the view

Work lessevolve

loose coupling

Work lessevolve

loose coupling

at least because we use a framework

Less work

because the hard work is delegated to the browser/proxy

http://www.flickr.com/photos/snakphotography/5004775320/sizes/o/in/photostream/

Evolve

because cache is abstracted from the application

Loose coupling

because caching is bound to the protocol, HTTP, not to your implementation ( Sf, RoR, Django )

but hey, you say

HTTP's cache fails when dealing with really dynamic pages, because consumers will always have to hit the

origin server, although a part of the page would be cacheable ( header and footer, for example )

ESI was built for thathttp://www.w3.org/TR/esi-lang

Edge Side IncludesA de facto standard for bla bla bla...

Server side includes ( not SSI! ) usually handled by the architecture's ESI processor.

http://www.w3.org/TR/esi-langhttp://www.w3.org/TR/edge-arch

<esi:include src="http://osidays.com/talks/1" />

1s (tweets)

3600 (post)

<esi:include src='tweets.html' />

<esi:include src='article/12.html' />

2. adaptability & durability

Hypermediaanother long-time friend

Linksoutrageously semplifying

HTTP/1.1 201 CreatedHost: www.example.comEtag: 1234X-Powered-By: php/5.3Location: /users/1

POST /usersHost: www.example.com

HTTP/1.1 201 CreatedHost: www.example.comEtag: 1234X-Powered-By: php/5.3Location: /users/1

HTTP/1.1 201 CreatedHost: www.example.comEtag: 1234X-Powered-By: php/5.3Location: /new-users-db/1

consumers of your API are able to followthe changes of your design

Client knows how to consume the service based on the informationsauto-provided by the service itself

No WSDL.

No URI templates.

No easily-outdated documentation.

No assumptions.

Less WTFs.

This does not easily break.

HATEOASHypermedia As The Engine Of Application State

everything seems eventually

Recap: why REST?Bengaluru, 20-22 November 2011

PerformancesBengaluru, 20-22 November 2011

Scalability

Durability

Not RESTful?

Simply don't care

Rules of architectural design

Follow them accordingto your needs

amazon.com

Alessandro Nadalin

odino.org

@_odino_ #osidays

@_odino_

Thank YOU!

Creditshttp://www.flickr.com/photos/larachris/16564077/sizes/o/in/photostream/

http://www.flickr.com/photos/ashatenbroeke/4367373081/sizes/z/in/photostream/http://www.flickr.com/photos/yourdon/3140270189/sizes/l/in/photostream/http://www.flickr.com/photos/jox1989/4964706072/sizes/l/in/photostream/http://www.flickr.com/photos/brainfg/168506259/sizes/o/in/photostream/

http://www.flickr.com/photos/norte_it/3897091546/sizes/o/in/photostream/http://www.zdnet.com/blog/service-oriented/soap-versus-rest-a-matter-of-style/3568

http://www.flickr.com/photos/turtlemom_nancy/2046347762/sizes/l/in/photostream/http://www.flickr.com/photos/juanpg/3333385784/sizes/z/in/photostream/http://www.flickr.com/photos/congvo/301678287/sizes/l/in/photostream/

http://www.flickr.com/photos/ihasb33r/2573196546/sizes/z/in/photostream/http://www.flickr.com/photos/martin_heigan/4544138976/sizes/o/in/photostream/

http://www.flickr.com/photos/cknara/4195099999/sizes/o/in/photostream/http://www.flickr.com/photos/1080p/3076529265/sizes/l/in/photostream/

http://www.flickr.com/photos/adamrice/280300202/sizes/l/in/photostream/http://www.flickr.com/photos/tomer_a/541411897/sizes/o/in/photostream/http://www.flickr.com/photos/subpra/4514008262/sizes/l/in/photostream/

http://www.flickr.com/photos/lippincott/2539720043/sizes/l/in/photostream/http://www.flickr.com/photos/rawryder/5086090931/sizes/l/in/photostream/http://www.flickr.com/photos/robboudon/5312731161/sizes/l/in/photostream/

http://www.flickr.com/photos/bc-burnslibrary/4158243488/sizes/o/in/photostream/http://www.flickr.com/photos/13606325@N08/2416993706/sizes/o/in/photostream/

http://www.flickr.com/photos/neothezion/5135841069/sizes/l/in/photostream/http://www.flickr.com/photos/planetschwa/2494067809/http://www.flickr.com/photos/thomasthomas/258931782/

http://www.flickr.com/photos/rustyboxcars/2629631562/sizes/l/in/photostream/http://www.flickr.com/photos/ell-r-brown/4138727474/sizes/l/in/photostream/http://www.flickr.com/photos/noah123/5082076630/sizes/z/in/photostream/http://www.flickr.com/photos/jungle_boy/220181177/sizes/l/in/photostream/

http://www.flickr.com/photos/prettydaisies/872539081/sizes/l/in/photostream/http://www.flickr.com/photos/kaptainkobold/76256150/sizes/o/in/photostream/

http://www.flickr.com/photos/uomoincravatta/1438372865/sizes/z/in/photostream/

REST in peace @ Osidays 2011 India 11-21-2011

Technology

Symfony2 - OSIDays 2010

REST in peace: a handbook of software waste @ Jazoon 2011 06-22-2011

THURSDAY Rest Rest Rest Rest Rest Month 1 FRIDAY HilT ... · PDF fileTHURSDAY Rest Rest Rest Rest Rest Month 1 FRIDAY HilT: Plyo I-IIIT: Plyo Combat 60 Combat 45 Combat 60 SATURDAY

The Rest of REST

REST in peace @ PHP.TO.START 07-11-2011

Renaplast - renacon.in · Rest Rest Rest Rest Rest Rest Rest Rest Rest Rest Ost Rest Rest Rest R.st Rest Rast Rest Rest Rest Rest Rest Rest Rest Rest Rest Rest Rest Rest

Rest. Hacienda Los Morales México D.F. 6 Octubre 2011

Rest Day Rest Day Rest Day Rest Day XT Plyo XT Plyo XT ... · Rest Day Rest Day Rest Day Rest Day XT Plyo XT Plyo XT Competition Core Ripped Conditioning + Ultimate Abs Ripped Conditioning

Errazudin - REST in pieces (with frapi) - Malaysia Open Source Conference 2011

REST-something-different (2011-05-12)

Rest Hour Sep 2011

Rest Day Rest Day Rest Day Rest Day Sprawl & Brawl ... · Rest Day Rest Day Rest Day Rest Day Sprawl & Brawl Competition Core Plyo XT Muay Thai Strength & Force Upper + Ultimate Abs

Vicente, Mª.T. et al. Nacionalismos como motor de la conserv. y rest. 2011

REST and REST-fulness

Developer Guide: OData SDK - Sybaseinfocenter.sybase.com/help/topic/com.sybase.info... · 6/28/2011 · REST SDK API Usage.....56 Rest Client API Reference for iOS.....56 Enabling

SUNDAY Rest Rest Rest Rest MONDAY Learn & Burn 20 Min Workout 20 Min Workout … · 2018-01-24 · SUNDAY Rest Rest Rest Rest MONDAY Learn & Burn 20 Min Workout 20 Min Workout Abs

Behördeninformation 24. Januar 2007 Rest. Schützenhaus in …¤sentation... · 2018. 8. 10. · GL 2011: 3 Gemeinden - 1 Kanton Behördeninformation 24. Januar 2007 Rest. Schützenhaus

Codecamp iasi-26 nov 2011-unit-testing-for-the-rest-of-us

SUNDAY Rest Rest Rest Rest My MONDAY Chest And Back Ab ... · SUNDAY Rest Rest Rest Rest My MONDAY Chest And Back Ab Ripper X Chest And Back Ab Ripper X Chest And Back Ab Ripper X

2011 - DNC: REST Wars