...
The system starts small and begins with a registration system.
| Hostname | Description | Naming Convention | |
|---|---|---|---|
S1 | Host system for Registration System. | Use a 2-3 letter convention to describe the host's main function. As the purpose of the host can easily change we use a generic name, S1 for system 1. | PRDRGH01WEB1|
PRD-RG-WEB1 | Runs Apache Web Server. | PRD or UAT = Production or UAT | H = Hardware = Physical Hardware or Hosting Site1 = The first virtual server with allowance for relation to a corresponding server, in this case just one application server | PRDRGH01APP1
PRD-RG-APP1 | Runs Tomcat Application Server and HypSQL Database Server. | This has both an application and database. Because the database is portable and more easier to move, we make the judgment call to name the system APP after the more primary long term function of the server. The convention follows but notice the 1 in MGH1V1APP1. The zero visually places this server with the correspond Web Server. |
Phase 2
At this point the hostnames are not too bad. Their real value comes when the system needs to grow.
The system grows and requires a second application server to manage the load. Usually new applications are added first as they generate the most load. Here is how it will look in a sorted list,
| Hostname | Description | Naming Convention | ||
|---|---|---|---|---|
S1 | Host system for Registration System. | Existing. | PRDRGH01WEB1||
PRD-RG-WEB1 | Runs Apache Web Server. | Existing. | PRDRGH01APP1||
PRD-RG-APP1 | Runs Tomcat Application Server and HypSQL Database Server. | Existing. | PRDRGH01APP2||
PRD-RG-APP2 | Runs Tomcat Application Server. | The first 01 in | PRDRGH01PRD-RG-APP2 shows that the server is related to the Web Server | PRDRGH01PRD-RG-WEB1. The last number, indicates this is the next application server in the series. |
The convention naturally sorts well. If you are reading this article off of the Confluence system, click the Hostname title on the table to see the list sorted. Now let's add something new to the mix.
...
There is need for a new system for migrating users to tokens which we'll call MG for migration. Notice that we use a generic name rather than TM as the system could evolve to do other types of migrations. The system is low budget and considered temporary. As such, the customer wants to reuse the web server PRDRGH1X01WEB1.
| Hostname | Description | Naming Convention | |||||
|---|---|---|---|---|---|---|---|
S1 | Host system for Registration System. | Existing. | PRDRGH01WEB1|||||
PRD-RG-WEB1 | Runs Apache Web Server. | Existing. | PRDRGH01APP1|||||
PRD-RG-APP1 | Runs Tomcat Application Server and HypSQL Database Server. | Existing. | PRDRGH01APP2|||||
PRD-MG-APP1 | Runs Tomcat Application Server | .Existing | PRDMGH01APP1 | Runs Tomcat Application Server and HypSQL Database Server. | Again the | 01 in PRDMGH01APP11 in PRD-MG-APP1 clearly shows that it is connected to | PRDRGH01WEB1PRD-RG-WEB1 and the MG indicates the systems primary function is for migrations |
Next phase is where the naming convention really shines.
...
Over time the system becomes more critical and has grown in number of users. The client agrees to buy new hardware, introduce a load balancer and a second web and application server. Also, as with many systems the MG temporary TM system becomes permanent.
Hostname | Description | Naming Convention | |
|---|---|---|---|
S1 | Host system for Registration System. | Existing. | PRDRGH01WEB1|
PRD-RG-WEB1 | Runs Apache Web Server. | Existing | PRDRGH01APP1|
PRD-RG-APP1 | Runs Tomcat Application Server and HypSQL Database Server. | Existing | |
| PRD-MG-APP1 | Runs Tomcat Application Server and HypSQL Database Server. | Existing | |
| PRD-RG-WEB2 | Runs Apache Web Server. | PRDRGH02APP1 | WEB2 is paired with APP2 |
| PRD-RG-APP2 | Runs Tomcat Application Server |
If you are reading this article off of the Confluence system, click the Hostname title on the table to see the list sorted. Notice that sorted, it is very clear how the systems relate to each other.
...