[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-10 (世界標準時間)。"],[],[],null,["# Key terms\n\nThis page provides key terminology that applies to Service Directory.\nReview these terms to better understand how Service Directory works.\n\nEndpoint\n\n: An endpoint is an individual IP/port pair fronting a service that can handle\n requests. Any given service can have zero or more endpoints. The endpoint\n can be a VM, container, load balancer, or other entity capable of handling\n the requests. An example would be a cluster of user-managed Redis servers.\n\n: Endpoints can have optional annotations, in the form of key:value pairs, that\n clients can use. For example, a Redis service might have an annotation\n like `replica:server`. Annotations can be used to store URLs. You can use a\n tool such as [jq](https://stedolan.github.io/jq/)\n to pull the new URL out of the response.\n\n: For Service Directory, an endpoint can only exist within a service and\n is identified with an endpoint name that is a string identifier that is unique\n to that service.\n\nService\n\n: A service is a collection of endpoints (IP/ports) that provide a set of\n behaviors. Clients look up a service by its name and then connect to the\n endpoints that provide that service. Services can also have optional\n annotations (key-value pairs) associated with them (for example,\n `use_https:true`).\n\n: A service must belong to a namespace. Each service name must be unique within\n that namespace.\n\nNamespace\n\n: A namespace holds a set of service names along with\n their endpoint information. A namespace is a means of grouping services\n together for easier management.\n\n: Namespaces are regional resources and belong to a project. The name of a\n namespace must be unique for that project and region.\n\n Although a namespace is a regional resource, the services that belong to that\n namespace can exist anywhere and be queried from anywhere. We recommend\n customers choose a region that maps to where their endpoints are running.\n\nHTTP/gRPC clients\n\n: Service Directory supports look up of service names using HTTP/gRPC.\n There are no requirements that the service and client be on the same network.\n\n: Lookup operations over gRPC are controlled by IAM.\n\nService Directory zone\n\n: A Service Directory zone is a specific type of [Cloud DNS private\n zone](/dns/docs/overview#concepts) whose complete and authoritative source of\n information is a Service Directory namespace. It allows you to look up\n Service Directory data using DNS requests.\n\n: If a namespace is attached to a Service Directory zone, then all\n services in that namespace are visible to all networks that are allowed to\n query the zone."]]