dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

mark review 

Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>
This commit is contained in:
Hannah Hunter 2024-02-06 12:44:20 -05:00
parent 330be0a82b
commit 2961bc4358
4 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md
View File

@ -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. **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. 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 ### Streaming for HTTP service invocation

10
daprdocs/content/en/operations/configuration/configuration-overview.md
View File

@ -190,11 +190,11 @@ The following table lists the properties for HTTP handlers:
See [Middleware pipelines]({{< ref "middleware.md" >}}) for more information 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 ```yaml
apiVersion: dapr.io/v1alpha1 apiVersion: dapr.io/v1alpha1
@ -209,7 +209,9 @@ spec:
connectionString: "/home/user/.dapr/nr.db" 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 #### Scope secret store access

4
daprdocs/content/en/reference/components-reference/supported-name-resolution/_index.md
View File

@ -7,10 +7,10 @@ description: The supported name resolution providers to enable Dapr service invo
no_list: true 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. 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/description.html" >}}
{{< partial "components/name-resolution.html" >}} {{< partial "components/name-resolution.html" >}}

4
daprdocs/content/en/reference/resource-specs/configuration-schema.md
View File

@ -47,8 +47,8 @@ spec:
- name: <HANDLER-NAME> - name: <HANDLER-NAME>
type: <HANDLER-TYPE> type: <HANDLER-TYPE>
nameResolution: nameResolution:
component: "sqlite" component: <NAME-OF-NAME-RESOLUTION-COMPONENT>
version: "v1" version: <NAME-RESOLUTION-COMPONENT-VERSION>
configuration: configuration:
connectionString: "/home/user/.dapr/nr.db" connectionString: "/home/user/.dapr/nr.db"
secrets: secrets: