Home
Join

5 Replies

  • I'd say depending on how much of a load you expect, sometimes the better option is an individual, separate server. I've read a few articles on this and that is what was recommended. Maybe if you have a high end server then of course, you can load more in the front or back.

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • I'm not familiar with system administrator habits or general administrative rules, but I'm a little worried that administrators don't want to open one more port. That might increase the risk?

    Was this post helpful? thumb_up thumb_down
  • There's ports open already you can randomize the port to mitigate that risk, but I'm not a security expert.

    Spice (1) flagReport
    Was this post helpful? thumb_up thumb_down
  • I can't randomly choose ports for a stable software, anyway, thank you

    Was this post helpful? thumb_up thumb_down
  • ares lee wrote:

    I can't randomly choose ports for a stable software, anyway, thank you

    I think he means to pick a port number at random and use that value in place of the standard one for your particular software, not to pick a port number at random for any given installation. That said, simply having another open port is not the issue security-wise. The security issue comes with having an insecure service that listens to traffic on that open port. You could have every single port on a networked system report as "open" but if nothing is listening to that port that is exploitable then there's no problem.

    To answer your original question, it really depends on the scale of the application. For most in-house stuff, having the database on the same server as the web page is just fine (and is going to be slightly more responsive). However, after a certain point, you're going to want a dedicated database server because you'll want it to have its own (ample) resources to use for the high volume of data requests rather than having to share those resources with the web server and then running into situations where either the web service starts becoming unresponsive due to the database doing extensive processing on complex queries or high volumes of traffic to various sites hosted on the server causing the database server to be slow to respond to queries.

    1 found this helpful thumb_up thumb_down

Read these next...