Streav
Streav

Architecture

Within this section, we provide an overview of the Streav platform architecture. We strongly advise a thorough reading of this section for a deeper understanding.

Streav architecture

Components

Streav Management

The Streav Management component serves as the dashboard for controlling the entire platform. It provides administrators with a centralized hub for managing various aspects of Streav. The corresponding Docker image is streav/management.

Streav Streaming

Streav Streaming is the component responsible for all operational processes and directly interfaces with clients. It handles the delivery of live and on-demand content. The associated Docker image is streav/streaming.

Streav API

The Streav API component acts as the bridge for 3rd party integrations, facilitating interaction between external services and the Streav platform. This component enables developers to extend the functionality of Streav by integrating with external systems. The corresponding Docker image for Streav API is streav/api.

Streav CLI

Streav CLI offers a command-line interface with functionalities for administrators to maintain Streav platform. The corresponding Docker image is streav/cli.

PostgreSQL

PostgreSQL serves as the database backbone for the Streav platform.

Redis

Redis functions as the platform's cache, enhancing performance by storing frequently accessed data in memory.

RabbitMQ

RabbitMQ facilitates communication between Streav's various components, ensuring coordination and data exchange. This message broker plays a crucial role in maintaining communication integrity and synchronization across the platform.

Notes

  • Streav Management is designed to be lightweight. It can efficiently run on as small as a VPS.
  • Due to its operational role and handling client-facing operations, Streav Streaming should be hosted on robust and powerful servers. The deployment scale should align with anticipated demands, ensuring optimal performance.
  • PostgreSQL, Redis, and RabbitMQ are the foundational components of the platform. Administrators can choose to self-host these components or use any cloud or managed service that aligns with their preferences and requirements.