[siong1987]

Have you tried using Rails engine for this or different components of your app?

It is actually pretty neat because the same login session can still be used within multiple engines. You can also release them as gems too.

I used to work on an enterprise app which we created the whole chat system with Rails engine. Then, we release the engine as a gem so that it can be used on the main app. I think it works quite well for us so far.

more info: http://stackoverflow.com/questions/6118905/rails-3-1-engine-...

[clizzin]

We do use a Rails engine for one of our components, but this isn't something we've explored a lot (or at least, I haven't personally; maybe some of the other Airbnb nerds will step in with their own thoughts). Even so, I don't see this as a good long-term solution for our architecture, mostly because not everything we do is Rails -- we currently run JVM services and Node.js services, for instance, and we'd like to keep things flexible in the future so we can always pick the best tool for a particular use case. Our routing service should be able to handle all those needs.

[jacquesc]

When they say gems, I would have to assume they mean rails engines since they mentioned they are using it to package up assets as well.

I've been using the same pattern. It works ok, but still feels clunky. ∞ bundle update. dev mode reloading for certain classes can be a major pain as well.