Video Streaming Server With Multi-Protocol,Robust And Rich API
Location：Index Page  >  Document  >  Architecture

Understanding the architecture of Ti Top Streamer from a technical perspective will greatly help you become more proficient in using it. If you are an engineer responsible for the operation and maintenance of this software, then it is even more important to understand its architecture. Only in this way can you deal with various possible problems more calmly. After all, at On-Premises scenarios, each client's operating environment (hardware, operating system, network, system configuration) has more or less differences.

Technicians familiar with software development may have a lot of experience with the term "architecture", Because "architecture" has many aspects, including logical architecture, physical architecture, and code level architecture. Since Ti Top Streamer is currently a commercial software, here we will focus more on introducing its physical architecture at the deployment level and logical architecture at the functional level, It will not involve topics like "using xxx technology when write the code". That is to say, what we are introducing here are all "applications" and "processes" that you can see and interact with, as well as the functions that you can experience, rather than code.

There is an obvious reason why you need to understand and be familiar with the architecture of Ti Top Streamer: It will make you more proficient in basic tasks such as installation, upgrading, uninstallation, service startup, and service shutdown.

Now, let's start with a serious introduction to "architecture", starting with a diagram：

For the architecture diagram above, let's provide a brief explanation：

1. The part inside the dashed box is the entire Ti Top Streamer, It consists of four parts: Streaming Engine,Config Server,Rest Server,Web Server. The Streaming Engine is an independent Linux process, while the other parts are another independent Linux process. These modules interact with each other through an HTTP interface.

2. The Streaming Engine and Configuration Server are the core components of the entire Ti Top Streamer. Streaming Engine provide the streaming service to the outside, The Config Server saves all configuration information, policy information (such as authentication information, source stream URL, etc.), and license information.

3. Rest Server is responsible for providing HTTP Rest services to external parties to achieve basic management and the workflow control, and it has no relation to the operation of video streams themselves。

4. Web Server is a web-based management console, that is a web control pannel for the administrator,With it, You will feel very convenient when use our software. Tips: The operation of Web Server depends on the operation of Rest Server, and you can understand it as a Web Application based on Rest Server.

Here are a few typical scenarios to introduce the internal workflow：

1. When the Streaming Engine starts, it sends an HTTP request to the Config Server to obtain the necessary information for operation,For example, what is the TCP port for the RTMP streaming service? What are the TCP ports for HLS and FLV streaming services? What is the License Key for the software? Is it online license or offline license? What source streams should be pulled from during startup?

2. After external encoders or mobile devices use the rtmp protocol to push streams to the Streaming Engine, the Engine will carry relevant parameters to initiate authentication requests to the Config Server, Then Config Server responds based on configuration information, The Streaming Engine decides whether to accept or reject streaming based on the response, and whether to forward the stream to a third-party system/CDN after accepting the streaming.

Other business scenarios are also similar. Just understand that the Streaming Engine is only responsible for streaming services, and all required configuration information and policy information are saved in the Config Server.