I heard that for java (jboss + any DB) it’s really important because there is going to be lot of problems, but for .net not so much, is it ?
Share
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.
I heard that for java (jboss + any DB) it’s really important because there is going to be lot of problems, but for .net not so much, is it ?
It’s all a matter of scalability. If you have an application with a very small userbase, small database with only a little bit of data, and basic application logic (like simple CRUD functionality), you probably aren’t going to gain very much by separating them. In an enterprise environment, with a large userbase, a gigantic database, and complex application logic, there will definitely be a benefit to physically separating them.