Exploding Rails

Active Record causes numerous problems within a Rails application. I cover a few of these in the talk, and show an alternate way of approaching the same problems.

Transcript

1. Exploding Rails
2. Rails: “Ge2ng started is easy” True / False?
3. Rails: “Ge2ng started is easy” True
5. Rails: “Applica=on maintenance is a cinch.” True / False?
7. Rails: “Applica=on maintenance is a cinch.” False
8. Ge2ng started is a one +me cost. Maintenance is forever.
9. Ac=ve Record is (mostly) to blame.
12. “Look at all the things I’m not doing.” “Provide sharp knives.”
13. Causes an N+1 query
14. Mixes database querying and data manipula=on
15. DB Calls Count: 3
16. “I’ll just stub those things out!”
18. Fixes the N+1 issue
20. Causes an N+1 query, also
21. SQL Query A view New in Rails 5.2 Query logging
22. Ac=ve Record is an an+-paBern.
23. Causes an N+1 query, also
25. Ac=ve Record violates SRP You, looking on in despair
26. Ac=ve Record =es your applica=on to your database.
27. Rails applica=ons know too much about their underlying database. (because Ac=ve Record makes it easy)
28. Rails has barely evolved.
29. Rails 1.2 Rails 5.2 app /controllers /helpers /models /views app /controllers /helpers /mailers /models /views
30. Does it go in the view? Does it go in the controller? Put it in the model No No
31. …
32. Have we learned nothing?
33. Rails as a delivery mechanism.
34. A browser Rails App Repos Database Rails Ruby PostgreSQL (duh) POROs Knows nothing about
35. Makes a request to… A browser Rails App Repos Database POROs
36. A browser Rails App Repos Database POROs Makes a request to…
37. A browser Rails App Repos Database POROs Makes a request to…
38. A browser Rails App Repos Database POROs Returns records
39. Returns en++es A browser Rails App Repos Database POROs
40. Returns data A browser Rails App Repos Database POROs
42. An En=ty
43. Projects::Project.new # => 12 methods My Rails App
44. Project.new # => 296 methods A Vanilla Rails App callbacks, dirty tracking, validations, etc.
45. DB Calls Count: 0
46. My Rails App
47. Regular Rails App
48. My Rails App
49. Regular Rails App
50. How did I get to this magical utopia?
51. ROM! http://rom-rb.org/
52. Exploded Rails app /controllers /helpers /models /relations /repositories /schemas /transactions /views Regular Rails 5.2 app /controllers /helpers /mailers /models /views
53. Repositories are the API between rela=ons and your applica=on.
54. Rela=ons are the API between repositories and your database.
55. Schemas validate data for your applica=on.
56. Transac=ons wrap complicated ac=ons into sensible steps.
57. A cleaner architecture.
58. Rails controllers know nothing about the database. (They only know about the repositories)
59. Rails views are unable to perform DB queries. (They accept what is given to them)
60. Rails models represent data and do nothing else. (No callbacks. No validation.)
61. Rails as a simple delivery mechanism.
62. I could go on…
63. Or you could read my app’s code: bit.ly/twist-v2 Uses Hanami + React
64. Or you could read my new book: bit.ly/exploding-rails $10 off Covers using rom-rb and dry-rb with Rails