Tag Info

New answers tagged

2

Long story short: all in one. If you consider one of these as "master" and the other as an augmented replica, that updates are replicated one way only, and you can survive large latencies in synchronisation (and I'll let you define "large") then two separate DBs will work. For anything else I'd suggest a single DB. If you have two-way updates will they be ...


2

Something to consider might be a Master Data Management (MDM) approach. It would basically consist of an operational data store for each application, each using an ETL job or replication to synchronize with a master data store. Each operational data store schema can evolve independently, with the ETL job handling any necessary translations. How often ...


2

I used to work on a similar application, but the anticipated situation in my application would be very different from the way this site, facebook, twitter, or your application would work. This is just in case, this can somewhat give you some insight. I put both authentication data and business data in the same SQL database. The reasons are: When the ...



Top 50 recent answers are included