@@ -48,7 +48,7 @@ the respective pattern.
48
48
### Resiliency against regional availability events
49
49
50
50
![ Regional
51
- Availability] ( media/event-hubs-federation-overview/regional-availability.jpg )
51
+ Availability] ( media/event-hubs-federation-overview/regional-availability.png )
52
52
53
53
While maximum availability and reliability are the top operational priorities
54
54
for Event Hubs, there are nevertheless many ways in which a producer or consumer
@@ -111,7 +111,7 @@ Guidance:
111
111
### Latency optimization
112
112
113
113
![ Latency
114
- Optimization] ( media/event-hubs-federation-overview/latency-optimization.jpg )
114
+ Optimization] ( media/event-hubs-federation-overview/latency-optimization.png )
115
115
116
116
Event streams are written once by producers, but may be read any number of times
117
117
by event consumers. For scenarios where an event stream in a region is shared by
@@ -133,7 +133,7 @@ Guidance:
133
133
134
134
### Validation, reduction, and enrichment
135
135
136
- ![ Validation, reduction, enrichment] ( media/event-hubs-federation-overview/validation-enrichment.jpg )
136
+ ![ Validation, reduction, enrichment] ( media/event-hubs-federation-overview/validation-enrichment.png )
137
137
138
138
Event streams may be submitted into an Event Hub by clients external to your own
139
139
solution. Such event streams may require for externally submitted events to be
@@ -157,7 +157,7 @@ Guidance:
157
157
158
158
### Integration with analytics services
159
159
160
- ![ Integration with analytics services] ( media/event-hubs-federation-overview/integration.jpg )
160
+ ![ Integration with analytics services] ( media/event-hubs-federation-overview/integration.png )
161
161
162
162
Several of Azure's cloud-native analytics services like Azure Stream Analytics
163
163
or Azure Synapse work best with streamed or pre-batched data served up from
@@ -179,7 +179,7 @@ Guidance:
179
179
180
180
### Consolidation and normalization of event streams
181
181
182
- ![ Consolidation and normalization of event streams] ( media/event-hubs-federation-overview/consolidation.jpg )
182
+ ![ Consolidation and normalization of event streams] ( media/event-hubs-federation-overview/consolidation.png )
183
183
184
184
Global solutions are often composed of regional footprints that are largely
185
185
independent including having their own analytics capabilities, but
@@ -202,7 +202,7 @@ Guidance:
202
202
203
203
### Splitting and routing of event streams
204
204
205
- ![ Splitting and routing of event streams] ( media/event-hubs-federation-overview/splitting.jpg )
205
+ ![ Splitting and routing of event streams] ( media/event-hubs-federation-overview/splitting.png )
206
206
207
207
Azure Event Hubs is occasionally used in "publish-subscribe" style scenarios
208
208
where an incoming torrent of ingested events far exceeds the capacity of Azure
@@ -230,7 +230,7 @@ Guidance:
230
230
231
231
### Log projections
232
232
233
- ![ Log projection] ( media/event-hubs-federation-overview/log-projection.jpg )
233
+ ![ Log projection] ( media/event-hubs-federation-overview/log-projection.png )
234
234
235
235
In some scenarios, you will want to have access to the latest value sent for any
236
236
substream of an event, and commonly distinguished by the partition key. In
0 commit comments