This message was imported from the Ruby/Rails Modularity Slack server. Find more info in the import thread.
Message originally sent by slack user U782WI24OVK
<@U7830DMKJNH> That’s interesting! Just read about CBRA and am wondering what are the advantages/differences vs a Rails engine based componetization. Maybe it’s easier to implement coming from an existing Monolith?
We’re kind of doing both. Our components are just gems and we sometimes use Railtie to hook-in to Rails or subclass Engine. Contracts have been helpful to expose a small interface without leaking implementation.
We sort of organically started extracting things towards engines. But it’s really a bit of a pain. Now we sort of do it the other way around, we really isolate features and domains into different engines/gems.
@stephan It’s just that Rails Engines are “native” to Rails and might have not been created specifically for solving the problems we’re concerned about, even though they do help to solve it
Oh no, sorry about the confusion. We’re talking about the same thing, I just had my first peak at CBRA yesterday and was only aware of Rails Engines before then. Hence my fuzzy comparison… Great to have you here!