Skip to content

Commit 8213f77

Browse files
committed
JPG -> PNG
1 parent f248080 commit 8213f77

15 files changed

+7
-7
lines changed

articles/event-hubs/event-hubs-federation-overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ the respective pattern.
4848
### Resiliency against regional availability events
4949

5050
![Regional
51-
Availability](media/event-hubs-federation-overview/regional-availability.jpg)
51+
Availability](media/event-hubs-federation-overview/regional-availability.png)
5252

5353
While maximum availability and reliability are the top operational priorities
5454
for Event Hubs, there are nevertheless many ways in which a producer or consumer
@@ -111,7 +111,7 @@ Guidance:
111111
### Latency optimization
112112

113113
![Latency
114-
Optimization](media/event-hubs-federation-overview/latency-optimization.jpg)
114+
Optimization](media/event-hubs-federation-overview/latency-optimization.png)
115115

116116
Event streams are written once by producers, but may be read any number of times
117117
by event consumers. For scenarios where an event stream in a region is shared by
@@ -133,7 +133,7 @@ Guidance:
133133

134134
### Validation, reduction, and enrichment
135135

136-
![Validation, reduction, enrichment](media/event-hubs-federation-overview/validation-enrichment.jpg)
136+
![Validation, reduction, enrichment](media/event-hubs-federation-overview/validation-enrichment.png)
137137

138138
Event streams may be submitted into an Event Hub by clients external to your own
139139
solution. Such event streams may require for externally submitted events to be
@@ -157,7 +157,7 @@ Guidance:
157157

158158
### Integration with analytics services
159159

160-
![Integration with analytics services](media/event-hubs-federation-overview/integration.jpg)
160+
![Integration with analytics services](media/event-hubs-federation-overview/integration.png)
161161

162162
Several of Azure's cloud-native analytics services like Azure Stream Analytics
163163
or Azure Synapse work best with streamed or pre-batched data served up from
@@ -179,7 +179,7 @@ Guidance:
179179

180180
### Consolidation and normalization of event streams
181181

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)
183183

184184
Global solutions are often composed of regional footprints that are largely
185185
independent including having their own analytics capabilities, but
@@ -202,7 +202,7 @@ Guidance:
202202

203203
### Splitting and routing of event streams
204204

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)
206206

207207
Azure Event Hubs is occasionally used in "publish-subscribe" style scenarios
208208
where an incoming torrent of ingested events far exceeds the capacity of Azure
@@ -230,7 +230,7 @@ Guidance:
230230

231231
### Log projections
232232

233-
![Log projection](media/event-hubs-federation-overview/log-projection.jpg)
233+
![Log projection](media/event-hubs-federation-overview/log-projection.png)
234234

235235
In some scenarios, you will want to have access to the latest value sent for any
236236
substream of an event, and commonly distinguished by the partition key. In
Binary file not shown.
132 KB
Loading
Binary file not shown.
71.7 KB
Loading
Binary file not shown.
91.3 KB
Loading
Binary file not shown.
96.4 KB
Loading
Binary file not shown.

0 commit comments

Comments
 (0)