← Back to Upcase

Combining three Rails apps into one container suite


(Steven Wanderski) #1

Hey guys,

Here is my dilemma in a nutshell: http://stackoverflow.com/questions/25165146/large-rails-suite-architecture-combine-three-apps-into-one-container-app

I really want to try the container approach which uses unbuilt engines as the major components (API, Admin, Models, etc). Pivotal Labs has a few write-ups about this approach (http://pivotallabs.com/migrating-from-a-single-rails-app-to-a-suite-of-rails-engines/). It sounds very interesting, but I’m sure there are downsides that I am not considering. My main concern / challenge is to properly isolate server resources to the API, separate from the Admin engine. On Heroku, can I run different server processes per engine?

Overall, do you guys think its a good idea to combine all three separate apps into one container? Since my main concern is making sure each component has enough resources, maybe I just make sure I have enough dynos to handle traffic?

I feel pretty strongly that my day-to-day development cycle will be happier using this approach. PS - currently, I am the sole Rails developer for this codebase.