Why not to use Rails? (actually it's when not to use Rails)

My Rails Israel 2012 conference talk.

Transcript

1. Rails Israel 2012 Why not to use Rails? Monday, November 12, 12
2. Arik Fraimovich @arikfr TRuby Podcast Monday, November 12, 12
3. actually... Why use Rails at all? Monday, November 12, 12
4. Monday, November 12, 12
5. • Community Monday, November 12, 12
6. • Community • Ruby Gems Monday, November 12, 12
7. • Community • Ruby Gems • Simplicity Monday, November 12, 12
8. • Community • Ruby Gems • Simplicity • Convention over configuration Monday, November 12, 12
9. • Community • Ruby Gems • Simplicity • Convention over configuration • Choices that are made for you Monday, November 12, 12
10. • Community • Ruby Gems • Simplicity • Convention over configuration • Choices that are made for you Monday, November 12, 12
11. Monday, November 12, 12
12. When not to use Rails? Monday, November 12, 12
13. general purpose libraries (gems) Monday, November 12, 12
14. for the simple stuff Monday, November 12, 12
15. for large web application or anything that isn’t a web application Monday, November 12, 12
16. “Our tools shape our thinking.” @drnic Monday, November 12, 12
17. Monday, November 12, 12
18. • Everything is sort of global, no need for require • (Usually) no namespacing • Everything in the context of HTTP request Monday, November 12, 12
19. No need to require? Monday, November 12, 12
20. • Sounds nice at the beginning No need to require? Monday, November 12, 12
21. • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww... No need to require? Monday, November 12, 12
22. • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww... • Slow boot time No need to require? Monday, November 12, 12
23. • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww... • Slow boot time • Slow specs No need to require? Monday, November 12, 12
24. • Sounds nice at the beginning • But then it starts to creep on you and everything becomes sllllowww... • Slow boot time • Slow specs • Slow everything No need to require? Monday, November 12, 12
25. Solution? Spork (Zeus?) Monday, November 12, 12
26. Solution? Spork (Zeus?) Monday, November 12, 12
27. The common Rails app. Monday, November 12, 12
28. The Rails app you want Monday, November 12, 12
29. Engines Monday, November 12, 12
30. Wagons Monday, November 12, 12
31. What about the everything in “HTTP context”? Monday, November 12, 12
32. Good question. Monday, November 12, 12
33. No good answers* * from me. yet. Monday, November 12, 12
34. Some Pointers Monday, November 12, 12
35. Some Pointers • Actor Model - “easy” concurrency. Popular implementation in Ruby: Celluloid Monday, November 12, 12
36. Some Pointers • Actor Model - “easy” concurrency. Popular implementation in Ruby: Celluloid • JRuby Monday, November 12, 12
37. Some Pointers • Actor Model - “easy” concurrency. Popular implementation in Ruby: Celluloid • JRuby • TorqueBox Monday, November 12, 12
38. Wrap up Monday, November 12, 12
39. • Use Rails, but remember there are other things out there Wrap up Monday, November 12, 12
40. • Use Rails, but remember there are other things out there • Use Rails “carefully”, as your project grows Wrap up Monday, November 12, 12
41. • Use Rails, but remember there are other things out there • Use Rails “carefully”, as your project grows • Don’t forget that not everything is a nail Wrap up Monday, November 12, 12
42. • Use Rails, but remember there are other things out there • Use Rails “carefully”, as your project grows • Don’t forget that not everything is a nail • And most important: keep using Ruby. It’s awesome Wrap up Monday, November 12, 12
43. Questions? @arikfr Monday, November 12, 12
44. • Architecture The Lost Years • Wrangling Large Rails Codebases • Hexagonal Rails • Celluloid • JRuby • TorqueBox • About concurrency and the GIL • Images taken shamelessly from Google. Monday, November 12, 12