From 2961bc43582b357ef1c160e7750a1ae38bb18865 Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Tue, 6 Feb 2024 12:44:20 -0500 Subject: [PATCH] mark review Signed-off-by: Hannah Hunter --- .../service-invocation/service-invocation-overview.md | 6 +++--- .../operations/configuration/configuration-overview.md | 10 ++++++---- .../supported-name-resolution/_index.md | 4 ++-- .../reference/resource-specs/configuration-schema.md | 4 ++-- 4 files changed, 13 insertions(+), 11 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md index 2f212e23d..a8c4ff039 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md +++ b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md @@ -90,13 +90,13 @@ The diagram below shows an example of how this works. If you have 1 instance of **Note**: App ID is unique per _application_, not application instance. Regardless how many instances of that application exist (due to scaling), all of them will share the same app ID. -### Pluggable service discovery +### Swappable service discovery -Dapr can run on a variety of [hosting platforms]({{< ref hosting >}}). To enable service discovery and service invocation, Dapr uses pluggable [name resolution components]({{< ref supported-name-resolution >}}). For example, the Kubernetes name resolution component uses the Kubernetes DNS service to resolve the location of other applications running in the cluster. +Dapr can run on a variety of [hosting platforms]({{< ref hosting >}}). To enable swappable service discovery with service invocation, Dapr uses [name resolution components]({{< ref supported-name-resolution >}}). For example, the Kubernetes name resolution component uses the Kubernetes DNS service to resolve the location of other applications running in the cluster. Self-hosted machines can use the mDNS name resolution component. As an alternative, you can use the SQLite name resolution component to run Dapr on single-node environments and for local development scenarios. Dapr sidecars that are part of the cluster store their information in a SQLite database on the local machine. -The Consul name resolution component can be used in any hosting environment, including Kubernetes or self-hosted. +The Consul name resolution component is particularly suited to multi-machine deployments and can be used in any hosting environment, including Kubernetes, multiple VMs, or self-hosted. ### Streaming for HTTP service invocation diff --git a/daprdocs/content/en/operations/configuration/configuration-overview.md b/daprdocs/content/en/operations/configuration/configuration-overview.md index e14067684..601f178ee 100644 --- a/daprdocs/content/en/operations/configuration/configuration-overview.md +++ b/daprdocs/content/en/operations/configuration/configuration-overview.md @@ -190,11 +190,11 @@ The following table lists the properties for HTTP handlers: See [Middleware pipelines]({{< ref "middleware.md" >}}) for more information -#### Name resolution +#### Name resolution component -You can set name resolution within the Configuration YAML. Set the `spec.nameResolution.component` property to `"sqlite"`, then pass configuration options in the `spec.nameResolution.configuration` dictionary. +You can set name resolution component to use within the configuration YAML. For example, to set the `spec.nameResolution.component` property to `"sqlite"`, pass configuration options in the `spec.nameResolution.configuration` dictionary as shown below. -This is the basic example of a Configuration resource: +This is the basic example of a configuration resource: ```yaml apiVersion: dapr.io/v1alpha1 @@ -209,7 +209,9 @@ spec: connectionString: "/home/user/.dapr/nr.db" ``` -See [the Name Resolution spec documentation]({{< ref supported-name-resolution >}}) and the [Configuration YAML documentation]({{< ref configuration-schema.md >}}) to learn more about how to configure name resolution per component. +For more information, see: +- [The name resolution component documentation]({{< ref supported-name-resolution >}}) for more examples. +- - [The Configuration YAML documentation]({{< ref configuration-schema.md >}}) to learn more about how to configure name resolution per component. #### Scope secret store access diff --git a/daprdocs/content/en/reference/components-reference/supported-name-resolution/_index.md b/daprdocs/content/en/reference/components-reference/supported-name-resolution/_index.md index fc072eab7..7ebd05eb9 100644 --- a/daprdocs/content/en/reference/components-reference/supported-name-resolution/_index.md +++ b/daprdocs/content/en/reference/components-reference/supported-name-resolution/_index.md @@ -7,10 +7,10 @@ description: The supported name resolution providers to enable Dapr service invo no_list: true --- -Name resolution is configured via the [Dapr Configuration]({{< ref configuration-overview.md >}}). - The following components provide name resolution for the service invocation building block. +Name resolution components are configured via the [configuration]({{< ref configuration-overview.md >}}). + {{< partial "components/description.html" >}} {{< partial "components/name-resolution.html" >}} diff --git a/daprdocs/content/en/reference/resource-specs/configuration-schema.md b/daprdocs/content/en/reference/resource-specs/configuration-schema.md index b10115fbc..6587863dc 100644 --- a/daprdocs/content/en/reference/resource-specs/configuration-schema.md +++ b/daprdocs/content/en/reference/resource-specs/configuration-schema.md @@ -47,8 +47,8 @@ spec: - name: type: nameResolution: - component: "sqlite" - version: "v1" + component: + version: configuration: connectionString: "/home/user/.dapr/nr.db" secrets: