Clarifies consumer groups and multiple instances (#1012)

This commit is contained in:
Mark Chmarny 2020-12-15 10:13:41 -08:00 committed by GitHub
parent 9fb926a0bc
commit f0d8999c35
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions

View File

@ -27,9 +27,10 @@ That means that when an application publishes a message to a topic using the Pub
### Consumer groups and multiple instances
The burden of dealing with concepts like consumer groups and multiple instances inside consumer groups is all catered for by Dapr.
The burden of dealing with concepts like consumer groups and multiple instances inside consumer groups is all handled autoamtically by Dapr:
When multiple instances of the same application ID subscribe to a topic, Dapr will make sure to deliver the message to only one instance. If two different applications with different IDs subscribe to a topic, at least one instance in each application receives a copy of the same message.
* When multiple instances of the same application (same IDs) subscribe to a topic, Dapr will deliver each message to only one instance of that application.
* If two different applications (different IDs) subscribe to the same topic, Dapr will deliver each message to only one instance of each application.
### Cloud events
@ -65,4 +66,4 @@ Limit which topics applications are able to publish/subscibe to in order to limi
## Next steps
- Read the How-To guide on [publishing and subscribing]({{< ref howto-publish-subscribe.md >}})
- Learn about [Pub/Sub scopes]({{< ref pubsub-scopes.md >}})
- Learn about [Pub/Sub scopes]({{< ref pubsub-scopes.md >}})