This is a topic for Ruby Summit 2018 this year, and with the shift of major technology stacks (frontend and Rust), it’s likely that sharing of Rails architecture will be more translator-related in the future (TAT I’m not defecting). Slides TAB here

The main thing to share is the Component Based Rails Application, which is actually a 13 year old concept.

  • The first book on this is Stephan Hagemann’s CBRA.
  • A new version of the book is now available on Amazon: www.amazon.com/… (The translator asked the publishing house, which seems hopeless).
  • Modular Rails Application by @t_dnzt
  • In addition, Root Car Insurance’s Rails team recently published The Modular Monolith: Rails Architecture also inspired me a lot. Their latest article Separating Data and Code in Rails impressed me with their concept of implementing Stateless Code.

At the end of the day, the main point I want to make about CBRA(Component Based Rails Application) is that it is “minimally painful” to simplify a huge, bloated monolith Application and set the stage for future split-up. On the other hand, what this talk doesn’t say is that componentized Rails development doesn’t have to start in the business, it still essentially gives you the option to plug-in some features.