Computer network naming scheme: Difference between revisions
imported>OAbot m Open access bot: url-access updated in citation with #oabot. |
imported>Citation bot Removed URL that duplicated identifier. Removed parameters. | Use this bot. Report bugs. | Suggested by Abductive | Category:Naming conventions | #UCB_Category 41/44 |
||
| Line 7: | Line 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). | 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 |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 | 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 |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 == | == Azure == | ||
Latest revision as of 08:11, 17 July 2025
Template:Refimprove 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 Microsoft Azure there is a naming convention to prefix applications with <templatestyles src="Mono/styles.css" />app-, functions app with <templatestyles src="Mono/styles.css" />func-, and service buses with <templatestyles src="Mono/styles.css" />sb-. The convention is to suffix the name with the environment <templatestyles src="Mono/styles.css" />-prod or <templatestyles src="Mono/styles.css" />-test and a number for the instance such as <templatestyles src="Mono/styles.css" />-001, <templatestyles src="Mono/styles.css" />-002, etc. Example <templatestyles src="Mono/styles.css" />app-navigator-prod-001.azurewebsites.net.[2][3]
See also
Script error: No such module "Portal".
References
<templatestyles src="Reflist/styles.css" />
Script error: No such module "Check for unknown parameters".