You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-features.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,8 @@ A **producer** (or publisher) is any application that sends events to an event h
59
59
60
60
:::image type="content" source="./media/event-hubs-features/partition_keys.png" alt-text="Diagram showing how partition keys map events to specific partitions.":::
61
61
62
+
<aname="publisher-policy"></a>
63
+
62
64
### Publisher policies
63
65
64
66
Publisher policies enable granular control when you have many independent publishers. Each publisher uses a unique identifier:
@@ -71,6 +73,8 @@ The publisher name must match the SAS token used for authentication. When using
71
73
72
74
---
73
75
76
+
<aname="event-consumers"></a>
77
+
74
78
## Consuming events
75
79
76
80
A **consumer** is any application that reads events from an event hub. Event Hubs uses a **pull model**—consumers request events rather than having events pushed to them.
0 commit comments