Difference between revisions of "IVS Wiki:Server Side Software Architecture"

From IVS Wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 16: Line 16:
  
  
<b>Web Server</b>
+
<b>Web Host</b>
 
*Serves the PHP-based application and user interface
 
*Serves the PHP-based application and user interface
 
*Powered by the Nginx web server
 
*Powered by the Nginx web server
Line 28: Line 28:
 
{{hr - 2}}
 
{{hr - 2}}
  
<b>Media Server</b>
+
<b>Streaming Engine</b>
 
*Manages communication with cameras
 
*Manages communication with cameras
 
*Handles video streaming to client PCs
 
*Handles video streaming to client PCs
Line 63: Line 63:
 
{{Manual lvl 2 | title = Deployment Models | content = }}
 
{{Manual lvl 2 | title = Deployment Models | content = }}
  
{{Float | content = {{img - resize | file = Network Architecture-One Server.webp | width = 300px}} }}
+
{{Float | content = {{img - resize | file = Network Architecture-One Server.webp | width = 300px | style = margin:0px 10px}} }}
 
{{Manual lvl 3 | title = Single Server | content =
 
{{Manual lvl 3 | title = Single Server | content =
 
The entire server-side software stack can be deployed on a single [[Servers | physical]] or [[VM - Main Page | VM]]. This configuration is suitable for smaller installations and environments with lower camera counts.
 
The entire server-side software stack can be deployed on a single [[Servers | physical]] or [[VM - Main Page | VM]]. This configuration is suitable for smaller installations and environments with lower camera counts.
Line 70: Line 70:
 
{{hr - 2}}
 
{{hr - 2}}
  
{{Float | content = {{img - resize | file = Network Architecture-Multi Server.webp | width = 300px}} }}
+
{{Float | content = {{img - resize | file = Network Architecture-Multi Server.webp | width = 300px | style = margin:0px 10px}} }}
 
{{Manual lvl 3 | title = Multi-Server | content =
 
{{Manual lvl 3 | title = Multi-Server | content =
 
For larger deployments—<em>such as those <b>exceeding 50 cameras</b> or spanning multiple departments</em>—the system supports a distributed architecture using multiple Media Servers.
 
For larger deployments—<em>such as those <b>exceeding 50 cameras</b> or spanning multiple departments</em>—the system supports a distributed architecture using multiple Media Servers.
Line 85: Line 85:
  
  
{{Top of Page}}
+
{{Top of Page}}</onlyinclude>}}
</onlyinclude>}}
 

Latest revision as of 17:26, 18 May 2026

Server Side Software Architecture

Our server-side software is built on a standard LEMP stack consisting of:

  • Linux
The application is designed to run on the latest Ubuntu Linux LTS (Server Edition).
  • Nginx
  • MySQL
  • PHP


⇧ Back to Top


Core Application Components

Web Host

  • Serves the PHP-based application and user interface
  • Powered by the Nginx web server

Database

  • Stores all unique, customer-specific configuration and application data
  • Implemented using MariaDB

Streaming Engine

  • Manages communication with cameras
  • Handles video streaming to client PCs
  • Responsible for recording, storage, and clip creation


⇧ Back to Top


Logical Server Architecture

The application is divided into two main server roles:


Application Server: The Application Server hosts the core application logic and includes:

  • PHP web pages served via Nginx
  • MariaDB services
  • Node.js messaging and control service

Media Server: The Media Server is responsible for all video-related operations, including:

  • Camera communication
  • Video stream distribution to clients
  • Recording management and clip generation


⇧ Back to Top


Deployment Models

Network Architecture-One Server.webp

Single Server

The entire server-side software stack can be deployed on a single physical or VM. This configuration is suitable for smaller installations and environments with lower camera counts.


Network Architecture-Multi Server.webp

Multi-Server

For larger deployments—such as those exceeding 50 cameras or spanning multiple departments—the system supports a distributed architecture using multiple Media Servers.


In this model:
  • One Application Server hosts the core application services
  • One or more dedicated Media Servers handle video processing and storage
  • Media Servers can be added incrementally to scale performance and capacity


🕮
This architecture provides flexibility, scalability, and efficient handling of high video workloads.


⇧ Back to Top