The document discusses best practices for developing large-scale Ruby on Rails applications. It emphasizes the importance of prioritizing performance and stability over new features by avoiding complexity, designing for caching, and using simple SQL queries. It also covers practices like continuous integration testing, remote testing, exception monitoring, feature flagging for prototypes, and automated deployment processes.

1. Large-scale web service
and operations
with Ruby
2011 7 19

2. 2011 7 19

3. I and
RubyKaigi
2011 7 19

4. 2011 7 19

5. 2011 7 19

6. 2011 7 19

7. 2011 7 19

8. Large-scale web service
and operations with
Ruby
2011 7 19

9. Large-scale web service
and operations with
Ruby
2011 7 19

10. Large-scale web service
and operations with
Ruby
2011 7 19

11. Large-scale web service
and operations with
Ruby
2011 7 19

12. 2011 7 19

13. 2011 7 19

14. 2011 7 19

15. 2011 7 19

16. 2011 7 19

17. 2011 7 19

18. Bringing smiles to everyone by
making every day cooking more
enjoyable.
2011 7 19

19. What is
COOKPAD?
2011 7 19

20. 2011 7 19

21. 12,300,000 UU (pc only)
1+ million Recipes
Used by 1 in 2 women
in their 30s
2011 7 19

22. 2011 7 19

23. 2011 7 19

24. 2011 7 19

25. 2011 7 19

26. 2011 7 19

27. 2011 7 19

28. 2011 7 19

29. 2011 7 19

30. Architecture based on best practices
2011 7 19

31. 2011 7 19

32. 2011 7 19

33. 2011 7 19

34. 2011 7 19

35. 2011 7 19

36. 2011 7 19

37. 2011 7 19

38. 2011 7 19

39. 2011 7 19

40. http://d3921.image.cookpad.com/
recipes/1237075/100x141c/
0b9c3ad1cba65869058e17cf78988bcb.jpg
2011 7 19

41. http://d3921.image.cookpad.com/
recipes/1237075/ 100x141c
/
0b9c3ad1cba65869058e17cf78988bcb.jpg
2011 7 19

42. ‘100’
‘100x100’
‘100x100c’
‘100x100c40_198_137_104_300’
2011 7 19

43. 2011 7 19

44. 2011 7 19

45. 2011 7 19

46. 2011 7 19

47. Easily customizable
search
2011 7 19

48. 2011 7 19

49. 2011 7 19

50. 2011 7 19

51. 2011 7 19

52. 2011 7 19

53. 2011 7 19

54. 2011 7 19

55. Architecture based on best practices
2011 7 19

56. “Good enough” is not good enough.
Always focus on what is best
2011 7 19

57. 2011 7 19

58. • Only add absolutely necessary features
• Avoid complexity
2011 7 19

59. • Design for caching
• Avoid complex SQL queries
2011 7 19

60. 2011 7 19

61. 2011 7 19

62. 2011 7 19

63. 2011 7 19

64. 2011 7 19

65. 2011 7 19

66. 2011 7 19

67. Development
2011 7 19

68. 2011 7 19

69. 2011 7 19

70. Working with Rails within a large team
2011 7 19

71. 2011 7 19

72. 2011 7 19

73. 2011 7 19

74. 2011 7 19

75. 2011 7 19

76. 2011 7 19

77. 2011 7 19

78. 2011 7 19

79. 2011 7 19

80. 2011 7 19

81. 2011 7 19

82. 2011 7 19

83. 2011 7 19

84. 2011 7 19

85. 2011 7 19

86. Run specs remotely
2011 7 19

87. $
rake
cookpad:spec:remote
2011 7 19

88. 2011 7 19

89. 2011 7 19

90. 2011 7 19

91. 2011 7 19

92. 2011 7 19

93. 2011 7 19

94. 2011 7 19

95. 2011 7 19

96. 2011 7 19

97. How did using a CI change our development flow?
Only release successful CI builds
Test coverage as a requirement
Tests should be written so they can run on a CI
2011 7 19

98. 2011 7 19

99. $
cap
production
deploy
Add a "deploy message" to every release
(ex: "Added feature x", "Fixed bug z" etc)
Skype notification
Mail sent to developer and support mailing lists
2011 7 19

100. 2011 7 19

101. 2011 7 19

102. 2011 7 19

103. It is nearly impossible to reduce number of exceptions to 0
Looking for spikes in number of exceptions is key
2011 7 19

104. 2011 7 19

105. 2011 7 19

106. 2011 7 19

107. Expands upon Rails functionality
Selective release of new features
(ex: “Show feature X only to users A, B, C)
Used for prototyping
Specs not required
If an exception occurs in an extension, it is turned off automatically
2011 7 19

108. 2011 7 19

109. 2011 7 19

110. new features
stats for staff
2011 7 19

111. 2011 7 19

112. How do we handle prototypes
we decide not to release?
2011 7 19

113. $
rm
app/extensions/
foobar_ext
2011 7 19

114. 2011 7 19

115. 2011 7 19

116. 2011 7 19

117. 2011 7 19

118. 2011 7 19

119. Thank You
2011 7 19

120. 2011 7 19