4 ms·
If you design your database with proper views and stored procedures, name spaced and permissioned correctly for the applications then any data model change that
by kasey_junk 12y ago
If 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.