Skip to content

Commit d3a99e4

Browse files
authored
Update streaming-endpoint-concept.md
1 parent b40f832 commit d3a99e4

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

articles/media-services/latest/streaming-endpoint-concept.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,6 @@ This section gives details about some of the Streaming Endpoint's properties. Fo
132132

133133
A single streaming endpoint can stream both live and on-demand videos and most customers only use one streaming endpoint. This section gives some examples of why you may need to use multiple streaming endpoints.
134134

135-
* To handle case of the streaming endpoint (origin) not being available or not having the requested content.
136135
* Each reserved unit allows for 200 Mbps of bandwidth. If you need more than 2,000 Mbps (2 Gbps) of bandwidth, you could use the second streaming endpoint and load balance to give you additional bandwidth.
137136

138137
However, CDN is the best way to achieve scale out for streaming content but if you are delivering so much content that the CDN is pulling more than 2 Gbps then you can add additional streaming endpoints (origins). In this case you would need to hand out content URLs that are balanced across the two streaming endpoints. This approach gives better caching than trying to send requests to each origin randomly (for example, via a traffic manager).

0 commit comments

Comments
 (0)