03 - Naming conventions
Third architecture decision should be about naming resources. There is one primary reason for it and that is that most resources cannot be renamed. And their recreation would cause huge headache.
Second reason is that we are unable to write descriptions, etc. to resources. So name should tell us all necessary information we need.
Microsoft provides two helpful documentations. First describe how we should construct the name and second provides us with default list of abbreviations for resources.
So it is ideal to decide that our naming convention will for example look like this:
appi-depositportal-uat-we
- appi (Application insight)
- depositportal (Service)
- uat (Environment)
- we (West Europe region)
Special cases
Unfortunately the convention above cannot be used everywhere, because some resources have special rules, like for instance storage accounts. Their name is shared between all tenants in region, max length of name is 24 letters and they cannot contain special characters, so at the end they need to look like this:
stCiklumDepositPortalUat