Difference between revisions of "Template talk:Server Side Software Architecture"

From IVS Wiki
Jump to: navigation, search
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
{{Article - Manual | content =  
+
{{Section | title = <h1>Server Side Software Architecture</h1> | content =
 +
Our server-side software is built on a standard <b>LEMP stack</b> consisting of:
 +
*<strong>Linux</strong>
 +
{{Float | content = {{Aside | style = max-width: 400px | content = The application is designed to run on the latest Ubuntu Linux LTS <em>(Server Edition)</em>.}} }}
 +
*<strong>Nginx</strong>
 +
*<strong>MySQL</strong>
 +
*<strong>PHP</strong>
  
−
<h1>Server Side Software Architecture</h1>
 
  
−
{{Aside | content = Our software is built on the standard <b>LEMP</b> <em>(Linux, Nginx, MySQL, and PHP)</em> architecture.}}
+
{{Top of Page}}
 +
{{hr}}
 +
 
 +
<center><h2>Core Application Components</h2></center>
 +
 
  
 +
<b>Web Server</b>
 +
*Serves the PHP-based application and user interface
 +
*Powered by the Nginx web server
  
−
The software has been designed to work on the latest LTS version of Ubuntu Linux <em>(Server Edition)</em>.  There are <b>3 main components</b> to the software application:
+
{{hr - 2}}
  
 +
<b>Database</b>
 +
*Stores all unique, customer-specific configuration and application data
 +
*Implemented using MariaDB
  
−
#<b>Web Server</b>: Serves the PHP-based application and user interface via Nginx.
+
{{hr - 2}}
−
#<b>Databas</b>e: Stores all unique, customer-specific information.
 
−
#<b>Media Server</b>: Manages communication with cameras and video streams delivered to client PCs, and handles recording and clip creation.
 
  
 +
<b>Media Server</b>
 +
*Manages communication with cameras
 +
*Handles video streaming to client PCs
 +
*Responsible for recording, storage, and clip creation
  
  
Line 18: Line 35:
 
{{hr}}
 
{{hr}}
  
 +
<center><h2>Logical Server Architecture</h2></center>
  
−
For networking purposes, there are 2 main components to the software application:
 
−
{{hr}}
 
−
<dl>
 
−
<dt>Application Server:</dt>
 
−
<dd>
 
−
This makes up the bulk of the application and consists of 3 primary components:
 
−
<ol>
 
−
<li><strong>PHP</strong> web pages being served up by the Nginx web server</li>
 
−
<li><strong>MySQL</strong> Database</li>
 
−
<li><strong>NodeJS</strong> messaging and control service</li>
 
−
</ol></dd>
 
  
−
{{hr - 2}}
+
The application is divided into two main server roles:
  
−
<dt>Media Server:</dt>
 
−
<dd>This portion of the application handles <u>all the communication with the cameras and video streams</u> being served out to the client PCs.  It also handles all the recording and clip creation.</dd>
 
−
</dl>
 
  
−
{{Aside - Helpful | content = From a physical or virtual server perspective, the <b>entire server side software stack can be run on a single server</b>.}}
+
<b>Application Server:</b>
 +
The Application Server hosts the core application logic and includes:
 +
*PHP web pages served via Nginx
 +
*MariaDB services
 +
*Node.js messaging and control service
  
 
{{hr - 2}}
 
{{hr - 2}}
  
−
For applications requiring <b>more than 50 cameras</b> or consisting of different departments the software can be broken out and additional Media Servers can be added.
+
<b>Media Server:</b>
 +
The Media Server is responsible for all video-related operations, including:
 +
*Camera communication
 +
*Video stream distribution to clients
 +
*Recording management and clip generation
  
−
<center>{{img - no_click | file = VALT Server Structure.png}}</center>
 
  
 +
{{Top of Page}}
 +
{{hr}}
  
 +
<center><h2>Deployment Models</h2></center>
  
  
 +
{{Float | content = {{img - resize | file = Network Architecture-One Server.webp | width = 300px}} }}
 +
<h3>Single Server</h3>
 +
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.
  
 +
{{hr - 2}}
  
 +
{{Float | content = {{img - resize | file = Network Architecture-Multi Server.webp | width = 300px}} }}
 +
<h3>Multi-Server</h3>
 +
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.
  
−
<h2>Single Server</h2>
 
  
−
From a physical or virtual server perspective the entire server side software stack can be run on a single server.
+
<div style="font-weight: bold; font-size: 1.1em">In this model:</div>
−
 
+
*One Application Server hosts the core application services
−
 
+
*One or more dedicated Media Servers handle video processing and storage
−
{{Top of Page}}
+
*Media Servers can be added incrementally to scale performance and capacity
−
{{hr}}
 
  
−
<h2>Multiple Servers</h2>
 
  
−
For applications that necessitate the use of over 50 cameras or encompass multiple departments, our software provides the option to distribute its functionality across multiple <b>"Media Servers"</b>. These dedicated servers are specifically designed to handle the crucial tasks of processing the video stream component of the VALT application and efficiently storing the associated video files. This multi-server architecture offers exceptional flexibility and scalability, accommodating diverse and expanding needs.
+
{{Aside - Helpful | content = This architecture provides flexibility, scalability, and efficient handling of high video workloads.}}
  
  
 
{{Top of Page}}
 
{{Top of Page}}
 
}}
 
}}

Latest revision as of 11:47, 16 February 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 Server

  • 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

Media Server

  • 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

Retrieved from "https://ipivs.info/wiki/index.php?title=Template_talk:Server_Side_Software_Architecture&oldid=16893"