...
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. |
RGH1V00WEB | Runs Apache Web Server. | Existing. |
RGH1V00APP | Runs Tomcat Application Server and HypSQL Database Server. | Existing. |
RGH1V01APP | Runs Tomcat Application Server. | The first 0 in MGH1V00APP shows that the server is related to the Web Server RGH1V00WEB |
The convention naturally sorts well. 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 RGH1V00WEB.
| Hostname | Description | Naming Convention |
|---|---|---|
S1 | Host system for Registration System. | Existing. |
RGH1V00WEB | Runs Apache Web Server. | Existing. |
RGH1V00APP | Runs Tomcat Application Server and HypSQL Database Server. | Existing. |
RGH1V01APP | Runs Tomcat Application Server.Existing | The first 0 in MGH1V00APP shows that the server is related to the Web Server RGH1V00WEB |
MGH1V00APP | Runs Tomcat Application Server and HypSQL Database Server. | Again the first 0 in MGH1V00APP clearly shows that it is connected to RGH1V00WEB and the MG indicates the systems primary function is for migrations |
Next phase is where the naming convention really shines.
Phase 4
Over time the system becomes more critical and has grown in number of users. The agrees to buy new hardware, introduce a load balancer and a second web and application server. Also, as with many systems the temporary TM system becomes permanent.
...