Computer network naming scheme: Difference between revisions
Wikipedia:Articles for deletion/Computer network naming scheme closed as no consensus (XFDcloser) |
Add text |
||
| Line 8: | Line 8: | ||
Naming systems have several other characteristics. The entities that assign and manage names can be [[Distributed computing|distributed]], [[centralized]], or [[hierarchical]]. Names can be human-readable or not human-readable.<ref>{{Cite journal |last1=Ahmed |first1=R. |last2=Boutaba |first2=R. |last3=Cuervo |first3=F. |last4=Iraqi |first4=Y. |last5=Tianshu Li |last6=Limam |first6=N. |last7=Jin Xiao |last8=Ziembicki |first8=J. |date=Third Quarter 2005 |title=Service naming in large-scale and multi-domain networks |url=https://ieeexplore.ieee.org/document/1610549 |journal=IEEE Communications Surveys & Tutorials |language=en |volume=7 |issue=3 |pages=38–54 |doi=10.1109/COMST.2005.1610549 |issn=1553-877X}}</ref> |
Naming systems have several other characteristics. The entities that assign and manage names can be [[Distributed computing|distributed]], [[centralized]], or [[hierarchical]]. Names can be human-readable or not human-readable.<ref>{{Cite journal |last1=Ahmed |first1=R. |last2=Boutaba |first2=R. |last3=Cuervo |first3=F. |last4=Iraqi |first4=Y. |last5=Tianshu Li |last6=Limam |first6=N. |last7=Jin Xiao |last8=Ziembicki |first8=J. |date=Third Quarter 2005 |title=Service naming in large-scale and multi-domain networks |url=https://ieeexplore.ieee.org/document/1610549 |journal=IEEE Communications Surveys & Tutorials |language=en |volume=7 |issue=3 |pages=38–54 |doi=10.1109/COMST.2005.1610549 |issn=1553-877X}}</ref> |
||
== Azure == |
|||
On Azure there is a naming convention to prefix applications with {{Mono|app-}}, functions app with {{Mono|func-}}, and service buses with {{Mono|sb-}}. The convention is to suffix the name with the environment {{Mono|-prod}} or {{Mono|-test}} and a number for the instance such a.s {{Mono|-001}}, {{Mono|-002}}, etc. Example {{Mono|app-navigator-prod-001.azurewebsites.net}}.<ref>{{cite web |title=Abbreviation recommendations for Azure resources - Cloud Adoption Framework |url=https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations |website=learn.microsoft.com |publisher=Microsoft |access-date=12 May 2025 |language=en-us}}</ref><ref>{{cite web |title=Define your naming convention - Cloud Adoption Framework |url=https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming |website=learn.microsoft.com |publisher=Microsoft |access-date=12 May 2025 |language=en-us}}</ref> |
|||
== See also == |
== See also == |
||
{{Portal|Internet}} |
|||
* [[Systematic name]] |
* [[Systematic name]] |
||
* [[Geospatial network]] |
* [[Geospatial network]] |
||
Revision as of 13:13, 12 May 2025
 | This article needs additional citations for verification. (August 2018) |
In computing, a naming scheme is a system for assigning and managing names of objects connected into computer networks. It typically consists of a namespace and processes for assigning, storing, and resolving names.
Naming schemes in computing
Server naming is a common tradition. It makes it more convenient to refer to a machine by name than by its IP address.
Network naming can be hierarchical in nature, such as the Internet's Domain Name System. Indeed, the Internet employs several universally applicable naming methods: uniform resource name (URN), uniform resource locator (URL), and uniform resource identifier (URI).
Naming systems have several other characteristics. The entities that assign and manage names can be distributed, centralized, or hierarchical. Names can be human-readable or not human-readable.[1]
Azure
On Azure there is a naming convention to prefix applications with app-, functions app with func-, and service buses with sb-. The convention is to suffix the name with the environment -prod or -test and a number for the instance such a.s -001, -002, etc. Example app-navigator-prod-001.azurewebsites.net.[2][3]
See also
References
- ^ Ahmed, R.; Boutaba, R.; Cuervo, F.; Iraqi, Y.; Tianshu Li; Limam, N.; Jin Xiao; Ziembicki, J. (Third Quarter 2005). "Service naming in large-scale and multi-domain networks". IEEE Communications Surveys & Tutorials. 7 (3): 38–54. doi:10.1109/COMST.2005.1610549. ISSN 1553-877X.
- ^ "Abbreviation recommendations for Azure resources - Cloud Adoption Framework". learn.microsoft.com. Microsoft. Retrieved 12 May 2025.
- ^ "Define your naming convention - Cloud Adoption Framework". learn.microsoft.com. Microsoft. Retrieved 12 May 2025.
External links
- RFC 2100 - "The Naming of Hosts"
- Naming conventions in Active Directory
- URIs, URLs, and URNs: Clarifications and Recommendations 1.0
 | This computer networking article is a stub. You can help Wikipedia by expanding it. |