sijie commented on a change in pull request #6286: Clarify documentation on 
Subscriptions, especially pub-sub vs queuing
URL: https://github.com/apache/pulsar/pull/6286#discussion_r377491047
 
 

 ##########
 File path: site2/docs/concepts-messaging.md
 ##########
 @@ -176,9 +176,11 @@ Topic name component | Description
 
 A namespace is a logical nomenclature within a tenant. A tenant can create 
multiple namespaces via the [admin API](admin-api-namespaces.md#create). For 
instance, a tenant with different applications can create a separate namespace 
for each application. A namespace allows the application to create and manage a 
hierarchy of topics. The topic `my-tenant/app1` is a namespace for the 
application `app1` for `my-tenant`. You can create any number of 
[topics](#topics) under the namespace.
 
-## Subscription modes
+## Subscriptions
 
-A subscription is a named configuration rule that determines how messages are 
delivered to consumers. There are four available subscription modes in Pulsar: 
[exclusive](#exclusive), [shared](#shared), [failover](#failover), and 
[key_shared](#key_shared). These modes are illustrated in the figure below.
+A subscription is a named configuration rule that determines how messages are 
delivered to consumers.  Each consumer may use a unique subscription name 
exclusive only to it, and then each consumer on the topic would receive all 
messages independent of other consumers (fan-out pub-sub messaging).  
Alternatively multiple consumers may use the same subscription name in either a 
shared or failover mode (message queuing). 
 
 Review comment:
   I am not sure this clarification here is clear enough. topic-subscription 
already indicates that messages are fan-out to different subscriptions. The 
clarification seems to be indicating it is one way or another. I would suggest 
just adding a tip at the end of this section.
   
   ```
   > If you want to achieve traditional "fanout pubsub messaging" among 
consumers, you can make each consumer ...
   > If you want to achieve "message queuing" among cnosumer, you can ...
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to