6 ms·
If the Rails and Laravel apps are updating the same tables in the database, or even different tables that have foreign key relations with each other, that is a
by kyllo 12y ago
If the Rails and Laravel apps are updating the same tables in the database, or even different tables that have foreign key relations with each other, that is a huge problem because changing the data layer in any way will require changing it in three places.
If they're confined to separate tables that happen to be in the same database, that's better. But then just putting them in different databases would potentially make configuration and deployment much easier.
There's really no valid reason to have two different app frameworks on top of a shared database.
- kasey_junk 12y agoIf you design your database with proper views and stored procedures, name spaced and permissioned correctly for the applications then any data model change that is not coupled in the data model need only be changed in the data store. If the data model itself is coupled then nothing you do will prevent the change crossing the application boundaries (and probably will propagate to more places). There are lots of valid reasons to have multiple app frameworks deal with a shared database. I mentioned one (transactionality) and there are many others.