Virtual Server – Key Things For You To Be Aware Of
A few words about a virtual server.
It’s an evident fact that shared hosting is probably the most common hosting service especially used by beginners. As usual such a server is connected to a good channel. On this server from several tens to hundreds of web projects can reside. They all use one WWW server, one FTP server, SQL server, one mail server and other support services.
The fact is that due to the modern implementation of these services or so called daemons they can be configured in such a way to provide their services directly to many users registered on the server. For example, a particular WWW server "knows" that the main page of the resource http://www.coolguy.net lies in the directory / user / www / coolguy and the main page of the project http://www.dudu.net can be found in / user / www /dudu. Similarly, the FTP server is configured so that when accessing the server via FTP and coolboy login, you can access / usr / www / coolboy. The similar principle refers to the login dudu. Mail servers also know their clients’ mailboxes and they can manage both incoming and outgoing messages properly
So, I’d like to stress that in the case of a normal hosting all projects are on the same server. Each of them has got its own directory. Of course, each project is limited to some disk quota, depending on the chosen tariff plan. The management of these entire systems is the responsibility of the administrator or the whole team of administrators of a particular hosting provider. It is clear that the main purpose of the administrator to maintain such things as external security, control inputs. It’s up to him to avoid overloading the server.
The task of ensuring the external security or in other words the resistance to network attacks is not a sort of headache just for hosting and it’s solved by standard methods. I mean timely updates, firewall configuration, monitoring logs, connections and so on.
Providing the same internal security is the problem which is considered to be more complicated, because it’s necessary to proceed from the fact that any user of the system having legal access to the server as can try to play a part of a "hacker" and attempt to gain access to documents of other projects that are on the same server. So it’s clear to you that either accidentally or intentionally, the user coolboy should not be able to read or modify the project documents belonging to the user dudu. Certainly he should be deprived of an opportunity to get into somebody’s mailbox, reading and modifying everything there. So it’s up to administrators to be concerned with this. As you can see this kind of web hosting is rather worth to try.
The majority of people assume that the choice of the best web hosting starts from reading the reviews. Well, the idea is not bad, but you can get into very big problems if you follow this idea.
The problem is that nowadays web hosting companies need to fiercely fight for the clients. And these companies cracked the review trick long ago: they are buying reviews or flood the market with fake reviews, that look like written by real clients. And they give a proud name of best web hosting even the junky service.
So, you really need to read the reviews, but don't be fused away with this best web hosting fancy wording - look into the core of it.
