Modularizing Rails Monoliths One Bite at a Time by Marc Reynolds

Rocky Mountain Ruby 2023 - Modularizing Rails Monoliths One Bite at a Time by Marc Reynolds
As Rails monoliths grow, coupling becomes increasingly difficult to manage. Many have reached for hope in microservices but instead found higher complexity. The Modular Monolith approach is a proven, lightweight alternative that offers the benefits of enforced boundaries without being cumbersome. This talk proposes a phased approach to refactoring toward this style using the packwerk gem.

[@leoluchi]

Nice topic, well explained

[@sunstrikovich]

Amazing talk! Thank you for sharing the experience

[@fuu812]

Thanks for this talk!

[@LouisNguyen-y5h]

Really nice 👍topic

[@stpaquet]

nice

[@Aalii6]

👍👍

[@zaqueudovale852]

Mudei meu projeto que usava exceptions pra usar a lib OneOf. Achei que fica mais claro no codigo os possiveis fluxos de execucao e tbm os casos de teste.

[@kevanschwitzer8585]

Not a rails developer, but great talk! Appreciated the insights!

[@BahriddinAbdiev]

This is great talk. Thank youIf you. I have a q: if you don't have database level constraints between tables (foreign key) you might have records which are stale. Then you should have some sort of syncing mechanism or dealing with bunch of rescue RecordNotFound errors. Isn't FK constraint actually good without cascade delete?