There are various standards for hostnames from complex to simple. This standard tries to achieve the following,
- Easy to use.
- Have consideration of "tying" machines together (for example, web to apps).
- Provide meaningful grouping when sorted in a list.
Samples
We start by providing some example models and see how the naming works as the system evolves.
Web Application Model
Here is a fictional registration system that would be Internet facing. As such, it will require a web server and an application server. The budget is small so the database will also reside with the application.
Phase 1
The system starts small and begins with a registration system.
At this point the hostnames are not too bad. Their real value comes when the system needs to grow.
Phase 2
The system grows and requires a second application server to manage the load. As in many cases, the application is the bottle neck. Here is how it will look in a sorted list,
The convention naturally sorts well. Now let's add something new to the mix.
Phase 3
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 evolved to do other types of migrations. The system is low budget and considered temporary. As such, the customer wants to reuse the web server.
T
..