Link to home
Start Free TrialLog in
Avatar of skyjumperdude
skyjumperdude

asked on

Web portal and database on same server

Hi All,

One of our developer is thinking of setting web portal which access a database for records on the same server as our database server. We had the web portal on another server from security purposes and that it won't put too much load on our database server but he is insisting to have them both on same server.

Can anyone please share your thoughts on this in regards to advantages and disadvantages? Please give your reasons in full details.

Thanks
Avatar of Scott Fell
Scott Fell
Flag of United States of America image

Would the web portal serve 100, 1,000 or 10,000 people at any given day?
Avatar of skyjumperdude
skyjumperdude

ASKER

May be 1000
ASKER CERTIFIED SOLUTION
Avatar of Dave Baldwin
Dave Baldwin
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I would agree with Dave.  Is there some function he thinks he needs by the move?
We need to provide our management team with a  proper document which proves our point.
That did not answer our question.  If the 'web portal' is already running, why does the developer think that it is worth the extra effort to move it?  Without any actual reason, it is just a waste of time to me.  What is the supposed benefit of moving it?
Well I don't have a clear answer from him but he thinks that out web portal will be faster since it is on the same server as the database server and when pulling records there won't be any traffic going through the network. He told the management team that it is better because it will be faster, better security and authentication.
Then you need to find out how much other traffic is going to the database server, how much memory the SQL Server normally uses (it typically uses a lot which will limit what is available to the web server), and point out that if the web portal is on the database server, that any break-in potentially gives them access to the databases.

A Google search will bring up many articles about doing it both ways.  The most frequent point about separating them is about security.  This can be an actual requirement depending on what is in your databases.
I am not a big server geek, I just use them, and my own web/data traffic in some instances is about the same to more.  I would consider 1000 people a day small unless they are all running some heavy queries with millions of rows of data and streaming output or you are using ms sql server with 2 gigs of ram.  

Most small dedicated servers have the db and webserver on the same box although now there seems to be a trend of having several drives where one is for the webserver, one for back up and an ssd for the database.   You don't start seeing separate box's until things start to grow.   But you are already there.

If you have everything local now, going to all in one would be a step back I think.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
skyjumperdude,

I would have thought you has been here long enough to know how the grading works in EE, obviously I was mistaken, so I would strongly suggest  you re-read the EE Guidelines and specifically the section What grade should I award?