split a database web application - good idea or bad idea?
Posted
by Khou
on Stack Overflow
See other posts from Stack Overflow
or by Khou
Published on 2010-05-04T03:11:15Z
Indexed on
2010/05/04
3:18 UTC
Read the original article
Hit count: 390
Is it a bad idea to split up a application and the database?
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?
© Stack Overflow or respective owner