Rails applications tend to grow and turn into massive monoliths–that’s a natural evolution of a Rails app, isn’t it?
What happens next is you starting looking for an architectural solution to keep the codebase maintainable. Microservices? If you brave enough…
Rails ecosystem already has a right tool for the job: engines. With the help of engines, you can split your application into independent parts combined under the same root application–the same way
rails gem combines all its sub-frameworks, which are engines too, by the way.
Curious how to do that? Come to hear how we’ve engine-ified our Rails monolith and what difficulties we faced along the way.
|The Gem Check: writing better Ruby gems||SouthEastRuby||August 2018|
|99 problems of slow tests||Paris.rb||June 2018|
|MetaCreativity||Saint-P RubyConf||June 2018|
|AnyCable: One cable to rule them all||RubyKaigi||May 2018|
|Take your slow tests to the doctor||BalkanRuby||May 2018|
|Access Denied: the missing guide to authorization in Rails||RailsConf||April 2018|
|Cables! Cables! Cables!||Wroc_Love.rb||March 2018|
|AnyCable: Universal Action Cable||RubyConfMY||October 2017|
|Faster Tests||RailsClub||September 2017|
|Writing better Ruby gems||Saint-P RubyConf||August 2017|
|Action Cable. Making Better||BRUG||May 2017|
|Real-time приложения. Модные фреймворки. Что дальше?||DUMP||April 2017|
|Run Test Run||RubyConfBY||April 2017|