Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
split a database web application – good idea or bad idea?
Application1 uses database1 on ServerX
Application2 uses database2 on ServerY
Both application communicates over web service API, they are apart of the same application,
one application is used to manage user’s profile/personal data, while the other application is used to manages user’s financial data.
Or should just put them together and just use 1 database on the same server?
That’s a question that nobody can answer unless we know the reason why they were split to begin with. For example, maybe the user’s financial info was kept separate due to legal or contractual/standards reasons (such as PCIDSS).