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

Tweaks per PR

This commit is contained in:
Phil Kedy 2021-09-14 16:38:29 -04:00
parent 477087cf8f
commit 6957a5c56a
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-route-messages.md
View File

@ -1,17 +1,13 @@
---
type: docs
title: "How-To: Route messages to different event handlers"
linkTitle: "How-To: Route events to different handlers"
linkTitle: "How-To: Route events"
weight: 2100
description: "Learn how to route messages from a topic to different event handlers based on CloudEvent fields"
---
## Introduction
[Content-based routing](https://www.enterpriseintegrationpatterns.com/ContentBasedRouter.html) is a messaging pattern that utilizes a DSL instead of imperative application code. PubSub Routing is an implementation of this pattern that allows developers to use expressions to route [CloudEvents](https://cloudevents.io) based on their contents to different URIs/paths and event handlers in your application. If no route matches, then an optional default route is used. This becomes useful as your applications expands to support multiple event versions, or special cases. Routing can be implemented with code; however, keeping routing rules external from the application can improve portability.
{{% alert title="Note" color="primary" %}}
This is an experimental feature. To enable it, add the `PubSub.Routing` feature entry to your application configuration.
This is an preview feature. To enable it, add the `PubSub.Routing` feature entry to your application configuration.
```yaml
apiVersion: dapr.io/v1alpha1
@ -23,6 +19,11 @@ spec:
- name: PubSub.Routing
enabled: true
```
## Introduction
[Content-based routing](https://www.enterpriseintegrationpatterns.com/ContentBasedRouter.html) is a messaging pattern that utilizes a DSL instead of imperative application code. PubSub routing is an implementation of this pattern that allows developers to use expressions to route [CloudEvents](https://cloudevents.io) based on their contents to different URIs/paths and event handlers in your application. If no route matches, then an optional default route is used. This becomes useful as your applications expands to support multiple event versions, or special cases. Routing can be implemented with code; however, keeping routing rules external from the application can improve portability.
{{% /alert %}}
This feature is available to both the declarative and programmatic subscription approaches.