New answers tagged

0

Here are my thoughts on this, 1. Via DB Side, If you don't want to mesh the deployment aspects with your application then this is best one. The system admin people will take care of these burden from you. They will setup the master-slave setup and your application will seamlessly access the db. 2. Spring - Hibernate In this way you can use interceptors ...


0

Yep. Setting up a master-slave is the easiest way to do this. If you need update or insert capability on both, that can be a bit tricky. In any case, if you do go master-slave, be aware that during the copy process the master DB will be lock



Top 50 recent answers are included