The document discusses REST (Representational State Transfer) and caching in a hypermedia system. It provides examples of how resources can link to other related resources and how caching can be implemented by having different versions of resources that are cacheable. Integrating systems over the web using hypermedia and REST principles is emphasized, with resources linking to each other to allow actions like cancelling flights or reservations through removing links.

1. Rest in Practice:
Hypermedia e Cache
Guilherme Silveira
@guilhermecaelum

2. Guilherme Silveira

3. 11 years, 1992: “Basic”

4. 2002 guj.com.br
2003 vraptor

5. 2004 extreme programming
2006 scrum
...

6. 2009 restfulie
http://restfulie.caelumobjects.com/

7. 2010 tectura
http://www.tectura.com.br

8. 2004 caelum - daily life
www.caelum.com.br

9. blogs
blog.caelum.com.br
agilenomundoreal.com.br
blog.caelumobjects.com

10. bank.com

11. bank.com calendar.com

12. bank.com calendar.com
travel.com

13. bank.com calendar.com
travel.com company.com

14. bank.com calendar.com
travel.com company.com

15. what is the future
of integration
over the web?

16. what was REST?

17. Restful Web
Services

18. Restful Web
create a saas account
Services

19. Restful Web
create a saas account
freeze account
Services

20. Restful Web
create a saas account
freeze account
Services
reactivate account

21. Web
Restful Services

22. Web
http
Restful Services

23. Web
http
port 80
Restful Services

24. Web
http
port 80
firewall heaven
Restful Services

25. Web Services
Restful

26. Web Services
xml, json
Restful

27. Web Services
xml, json
Restful
get, post, ...

28. DESAFIO 1

29. rest
=
web services

30. não

31. unresttrips.com: flight details
<?xml version="1.0" encoding="UTF-8" standalum="yes"?>
<flight>
<information>
<from>sao paulo</from>
<to>seoul</to>
</information>
<value>900.00</value>
</flight>

32. service locator when integrating:
coupling++
unrest
pay
unresttrips.com
guilherme

33. service locator when integrating:
coupling++
unrest
pay
unresttrips.com
guilherme

34. resttrips.com: flight details
<?xml version="1.0" encoding="UTF-8" standalum="yes"?>
<flight>
<information>
<from>sao paulo</from>
<to>seoul</to>
</information>
<value>900.00</value>
<link rel="payment"
href="http://resttrips.com/payment/custom"/
</flight>

35. resttrips.com: making the payment
flight = Client.at('http://resttrips.com/f/574XR4').get();
confirmation = flight.getLink("payment").
patch(cardInformation, value);

36. resttrips.com: changing its payment provider
<?xml version="1.0" encoding="UTF-8" standalum="yes"?>
<flight>
<information>
<from>sao paulo</from>
<to>seoul</to>
</information>
<value>900.00</value>
<link rel="payment"
href="http://paysite.com/custom"/>
</flight>

37. dependency injection when integrating:
coupling--
restrips
pay
resttrips.com
guilherme
paysite.com

38. dependency injection when integrating:
coupling--
restrips
pay
resttrips.com
guilherme
paysite.com

39. DESAFIO 2

40. adicione 1 link

41. mas

42. eu não viajo sozinho

43. meu amigo
sergio

44. resttrips.com: sharing a trip
flight = Client.at('http://resttrips.com/f/574XR4').get();
confirmation = flight.getLink("payment").
patch(cardInformation, value/2);
// send the payment link to another part of the web
flight = Client.at('http://resttrips.com/f/574XR4').get();
confirmation = flight.getLink("payment").
patch(cardInformation, value/2);

45. resttrips.com: sharing a trip
flight = Client.at('http://resttrips.com/f/574XR4').get();
confirmation = flight.getLink("payment").
patch(cardInformation, value/2);
// send the payment link to another part of the web
flight = Client.at('http://resttrips.com/f/574XR4').get();
confirmation = flight.getLink("payment").
patch(cardInformation, value/2);

46. resttrips.com: sharing a trip
flight = Client.at('http://resttrips.com/f/574XR4').get();
confirmation = flight.getLink("payment").
patch(cardInformation, value/2);
// send the payment link to another part of the web
flight = Client.at('http://resttrips.com/f/574XR4').get();
confirmation = flight.getLink("payment").
patch(cardInformation, value/2);

47. calendar: integrating my systems
myself = Client.at('http://users.calendar.com')
.with(auth).get();
myself.link("calendar").patch(flight.link("self"));

48. calendar: integrating my systems
myself = Client.at('http://users.calendar.com')
.with(auth).get();
myself.link("calendar").patch(flight.link("self"));

49. calendar: more examples
me.link("calendar").patch(link_to_birthday_list)
me.link("calendar").patch(link_to_hotel_reservation)
me.link("calendar").patch(link_to_trip_details)

50. so what?

51. Any update on the flight ==> reflects here
Any update on the hotel ==> reflects here
Any update on the meeting ==> reflects here
so what?

52. DESAFIO 3

53. DESAFIO 3 e 4

54. Any update on the flight ==> reflects here
Any update on the hotel ==> reflects here
Any update on the meeting ==> reflects here
so what?

55. Any update on the flight ==> reflects here
!
Any update on the hotel ==> reflects here
te
Any update on the meeting ==> reflects here
g ra
in t e
s e ,
st u
’t ju so what?
d o n

56. Remove ==> Cancels the flight
Remove ==> Cancels the reservation
Remove ==> Emails your coworkers
so what?

57. Remove ==> Cancels the flight
l!
Remove ==> Cancels the reservation
ro
Remove ==> Emails your coworkers
t
co n
l iz e
tr a
ce n
o n’t so what?
d

58. so what? that was just keeping an URI.
ro l!
co nt
a li ze
en tr
no tc
o
dRemove ==> Cancels the flight
Remove ==> Cancels the reservation
Remove ==> Emails your coworkers

59. DESAFIO 5

60. nosso sistema
‘rest’ funciona
assim?

62. misc

63. #json, #xml,
#soap #etc?

64. which #json, #xml
#etc?

65. micro formatos

66. atom

67. calendars

68. must ignore

69. integration over the web

70. integration over the web

71. cache

72. mov 2011 RELATÓRIO
detalhes
mov 2011
detalhes
mov 2011
detalhes

73. mov 2010 RELATÓRIO
detalhes
mov 2010
detalhes
mov 2010
detalhes

74. pagine!

75. pagine!
mov 2011
mov 2011
mov 2010
pagina 1

76. pagine!
mov 2011
mov 2011 mov 2010
mov 2010 mov 2010
pagina 1 pagina 2

77. pagine!
A!
AC
C
mov 2011
mov 2011 mov 2010
mov 2010 mov 2010
pagina 1 pagina 2

78. pagine!

79. pagine!
mov 2011
mov 2011
pagina 1

80. pagine!
mov 2010
mov 2011
mov 2010
mov 2011
mov 2010
pagina 1 pagina ano anterior

81. pagine!
t u !
u n i
B
mov 2010
mov 2011
mov 2010
mov 2011
mov 2010
pagina 1 pagina ano anterior

82. quebre!
mov 2010
mov 2010
mov 2010
mov 2010

83. quebre!
mov 2010
detalhes
mov 2010
mov 2010
mov 2010

84. quebre!
LINK!!!
mov 2010
detalhes
mov 2010
mov 2010
mov 2010

85. quebre!
Q ?
? P
LINK!!!
mov 2010
K
detalhes
I N
mov 2010
L mov 2010
mov 2010

86. quebre! O
R N
E T E
H ELINK!!!
mov 2010
detalhes
AC
C
mov 2010
mov 2010
mov 2010

87. quebre! O
R N
E T E
H ELINK!!!
mov 2010
detalhes
AC
C
mov 2010
mov 2010
mov 2010

88. quebre! O
R N
who E T E
H
wanELINK!!!
mov 2010
detalhes
C ts
Ao
C f to
mov 2010
rev live
er?
mov 2010
mov 2010

89. UM LINK POR VERSÃO

90. cache
não pode cachear?
acredite. você pode!
cacheie

91. bottom up
design by committe
mime type?
microformat
controlled vocabulary

92. hypermedia
integration over the web

93. hypermedia
R E
E B
Q U
integration over the web

94. LIN RE
hypermedia
E
KEB
Q U
integration over the web

95. LIN RIE
hypermedia
E E
E
K
CEHB
Q
C U
A
integration over the web

96. @guilhermecaelum
http://www.caelum.com.br
obrigado