How the web, and REST ideas, are currently applied to nosql databases and how we could improve this usage.

1. Arquiteturas
Contemporâneas
nosql + rest
guilherme.silveira@caelum.com.br

2. escalar na vertical

3. escalar = troca?

4. escalar = troca?

5. escalar = troca?

6. escalar = troca?

7. escalar = troca?

8. escalar = troca?

9. escalar = troca?

10. escalar = troca?

11. escalar = troca?

12. escalar = troca?

13. escalar = troca?

14. escalar = troca?

15. escalar = troca?

16. escalar = troca?

17. escalar = troca?

18. escalar = troca?

19. escalar = troca?

20. escalar = vazão

21. web

22. client server

23. stateless

24. statefull

25. X
statefull

26. cache

27. (clients)

28. (intermediates)

29. sem o cliente saber

30. uniform interface

31. (visibility)

32. layered system

33. don’t do it

34. don’t do it

35. (transformations)

36. (transformations)

37. (transformations)

38. code on demand

39. code on demand

40. code on demand

41. easy
human web

42. difficult
machine to machine

43. e aqui?

44. então...

45. #1

46. web scaling

47. don’t even ask,
cache

48. don’t hit your data,
cache

49. hit, but don’t reload

50. always challenge
ourselves

51. couchFulie
couch extension to keep restifying it

52. #1

53. uniform interface
move? copy?

54. webdav

55. #2

56. uri pattern
evolution is not based on uri patterns

57. hypermedia

58. less coupling

59. tight coupling raises
nasty issues in the long
term

60. neo4J

61. tá lá, na lata!

62. tá lá, na lata!

63. siga, descubra...

64. vai ficar lento...

65. e

66. vai ficar lento...

67. good relations

68. #3

69. attachment

70. hypermidia
nunca pensamos nela

71. #4

72. link revision history
RFC-5829

73. #5

74. locking
_rev = ... => ETag
unless / if ==> Not modified

75. Roy Fielding PHD Dissertation, 2000

76. headers ~ 1999

77. headers ~ 1999

78. #6

79. ia ficar lento, não ia?

80. media type
represent graph related issues
as queries, into a media type

81. #7

82. your job is not to cache

83. your job is not to cache

84. your job is not to cache

85. tell me when to cache

86. I don’t want to hit you!

87. “Polling the CouchDB server is not a good thing to do. Setting up new HTTP
connections just to tell the client that nothing's happened puts unnecessary
strain on CouchDB.” - CouchDB Wiki
http://wiki.apache.org/couchdb/HTTP_database_API

88. “Polling the CouchDB server is not a good thing to do. Setting up new HTTP
connections just to tell the client that nothing's happened puts unnecessary
strain on CouchDB.” - CouchDB Wiki
http://wiki.apache.org/couchdb/HTTP_database_API

89. “Polling the CouchDB server is not a good thing to do. Setting up new HTTP
connections just to tell the client that nothing's happened puts unnecessary
strain on CouchDB.” - CouchDB Wiki
http://wiki.apache.org/couchdb/HTTP_database_API

90. “Polling the CouchDB server is not a good thing to do. Setting up new HTTP
connections just to tell the client that nothing's happened puts unnecessary
strain on CouchDB.” - CouchDB Wiki
http://wiki.apache.org/couchdb/HTTP_database_API

91. “Polling the CouchDB server is not a good thing to do. Setting up new HTTP
connections just to tell the client that nothing's happened puts unnecessary
strain on CouchDB.” - CouchDB Wiki
http://wiki.apache.org/couchdb/HTTP_database_API

92. READ READ READ

93. mysql, couchdb
outros

94. proposta
de
mudança

95. cache

96. cache

97. cache

98. cache

99. você pode

100. vendor
lock-in
REST Arquitetura Irresponsável
Www.caelum.com.br

101. mas me diga

102. je doit cacher

103. o cache somos nozes
(web 2.0, shoes)

104. COMO
DORMIR
TRANQUIL
io O:
[ ]
o
rges
slé p NÃO
REINVENTE
A WEB

105. agradecimento
@porcelli

106. +

107. e .
]
rm
e ira .
ilh e m
[
gusilvelu r
OBRIG
@c a
com.b
ADO!