Service Directory

gcp Coordination servicegoogle-service-directory

Managed service registry resolvable over HTTP, gRPC and DNS.

Provider: gcp
Kind: Coordination service
Category: Operations
Official docs: https://cloud.google.com/service-directory/docs/overview

Properties · 3 set by this component

property	type	values	required	kind default	this component
consensus	enum	none \| raft \| paxos \| zab	no	none	inherited
dnsZoneBinding · component property	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
nodes	integer	—	no	—	inherited
replicated	boolean	—	no	false	▸ true
resolution · component property	enum	http \| grpc \| dns	no	http	inherited
role	enum	metadata \| lock \| discovery \| placement \| sharding \| leader-election \| config	yes	—	▸ discovery

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Shared dependency without redundancyerror

shared-dependency-without-redundancy

The design requires redundant discovery, but this DNS or coordination service, which everything depends on, runs on a single provider or a single replica. Its failure is the whole system's failure.

— all of these hold:
— the design requirement `availability.discoveryRedundant` is true
— any of these hold:
— the node's `redundantProviders` is false
— the node's `replicated` is false

Stateful engine pinned to a single zoneerror

stateful-engine-pinned-to-single-zone

A matching engine, coordination service or event store living in exactly one availability zone, with no failover and no replication, is lost with that zone. Everything that depends on it stops with it.

— all of these hold:
— the node sits inside exactly 1 availability-zone group
— any of these hold:
— the node's `failover` is "none"
— the node's `replicated` is false
— the node's `replication` is "none"

Use it in a design

nodes:
  - { id: "service-directory", component: "google-service-directory" }

Other Coordination service products · 17

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Service Directory namespace: a managed service registry resolvable over HTTP, gRPC and DNS.
3# Defaults from "Service Directory overview": fully managed, Google handles availability, redundancy and scaling; DNS resolution comes from a Cloud DNS private zone bound to the namespace.
4schemaVersion: "1"
5type: "component"
6id: "google-service-directory"
7kind: "coordination-service"
8provider: "gcp"
9docs: "https://cloud.google.com/service-directory/docs/overview"
10defaults:
11  managed: true
12  role: "discovery"
13  replicated: true
14properties:
15  resolution:
16    type: "enum"
17    values: ["http", "grpc", "dns"]
18    default: "http"
19  dnsZoneBinding:
20    type: "boolean"
21    default: false

The same page as markdown, for an agent: /catalogue/components/google-service-directory.md