Computer network naming scheme: Difference between revisions

Revision as of 02:37, 29 April 2024

Latest revision as of 08:11, 17 July 2025

(5 intermediate revisions by 4 users not shown)

Line 1:

<!-- Please do not remove or change this AfD message until the discussion has been closed. -->

{{Article for deletion/dated|page=Computer network naming scheme|timestamp=20240427233726|year=2024|month=April|day=27|substed=yes}}

<!-- Once discussion is closed, please place on talk page: {{Old AfD multi|page=Computer network naming scheme|date=27 April 2024|result='''keep'''}} -->

<!-- End of AfD message, feel free to edit beyond this point -->

{{Refimprove|date=August 2018}}

In [[computing]], a '''naming scheme''' is a system for assigning and managing names of objects connected into [[computer network]]s. It typically consists of a [[namespace]] and processes for assigning, storing, and [[Name resolution (computer systems)|resolving]] names.

Line 11 ⟶ 7:

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 computing|distributed]], [[centralized]], or [[hierarchical]]. Names can be human-readable or not human-readable.<ref>{{Cite journal |lastlast1=Ahmed |firstfirst1=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=http://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 [[Microsoft 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 as {{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 ==

{{Portal|Internet}}

* [[Systematic name]]

* [[Geospatial network]]