ruby - Running new rails app *and* legacy app on top of the same database -


i'm working on project we're building several new rails apps intended launched running along side legacy app need use same database. legacy database uses oracle.

i believe ideal cut-over cleanly , not have both new , legacy apps running on same db, in case it's not possible. legacy app large , runs pretty complex system that's core of business. intention replace bit @ time.

but require launch rails apps each handling part of application -- , sharing database operating legacy app.

i've looked around quite bit , haven't been able find definitive rails docs describing issues might run -- or if it's possible. know heroku supports running multiple rails apps pointing @ single database. i've found lots of discussion on people doing this, nothing pinpoints potential risks are.

is possible? specific problems occur?

edit: clarify, legacy application not rails-based. it's based on different technology.

while possible, you'll have careful, if have 2 systems performing migrations on same tables.

ideally 1 application "owns" database , assumes responsibility migrating various tables, it's possible split tables owned 1 application , other. schema_migrations table should able track these independently.

you run trouble if have make modifications same table in both applications there no way ensure 1 modification made before other, migration chains independent.

if you're careful avoid sort of thing, it's fine.

be sure have robust test environment simulate happens when both applications exercised in tandem.


Comments

Popular posts from this blog

java - Jmockit String final length method mocking Issue -

asp.net - Razor Page Hosted on IIS 6 Fails Every Morning -

c++ - wxwidget compiling on windows command prompt -