Optimize Video Delivery with Live Streaming

Explore how edge computing optimizes live streaming with HLS, real-time transcoding, and adaptive bitrate streaming for seamless, scalable, and secure content delivery.

View as Markdown

Edge computing transforms live streaming delivery by optimizing the distribution of high-quality video content. This architecture leverages advanced features like real-time transcoding and adaptive bitrate streaming, which, along with intelligent caching, enable seamless experiences for viewers. The distributed nature of edge computing allows for content to be processed and stored closer to the user, reducing latency and bandwidth constraints, and ensuring a high-quality stream even during periods of high demand.

This solution is ideal for content providers who require high fidelity and low latency for live events, e-sports, and educational content. Utilizing a network of edge locations, the platform ensures efficient delivery and scalability, while providing enhanced security features for stream protection.

Live Streaming Delivery Architecture Diagram

Architecture diagram

Live Streaming Delivery Dataflow

  1. The client (player) initiates a request to access a live stream.
  2. The request reaches the healthiest edge node, which is part of Azion’s globally distributed Global Infrastructure.
  • The application processes the request through the Rules Engine, applying security measures, origin configurations, and caching policies.
  1. If the requested stream content is cached in the Cache (recently received live content), it’s immediately delivered to the client.
  2. If the content isn’t cached, the request is forwarded to the ingest component within the Azion Web Platform.
  3. The source generates the content (video/audio).
  • The encoder converts the content into a data package in RTMP or HLS format and sends it to the Azion for Ingestion.
  1. The Ingest component (Live Ingest for RTMP or Tiered Cache for HLS) receives the encoded transmission, processes it, and answers to the edge node in HLS format (the same package is reutilized for all the edge nodes).
  2. The transcoded stream is cached in the Cache for subsequent high-demand simultaneous client requests.
  3. The Rules Engine may be programmed to intercept errors, apply additional rules, process HTTP response headers, etc.
  4. The processed transmission is delivered to the client, completing the live-streaming process. The user plays the content.

Components

  • Applications allows you to build applications on top of the Azion Web Platform and deliver your content.
    • Cache enables you to configure how your application caches content to reduce latency and increase transfer rates.
    • The Ingest component receives signal from encoders and distributes content in HLS format. It works as the origin for the application.

Implementation

  1. Create an application.
  2. Create a domain and associate it with the application.
  3. Set up and enforce cache policies for HLS in the application.
  4. Configure your source and encoder pointing to Azion Ingest DNS entries.
  5. Stream your content via Azion Web Platform.