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

From IVS Wiki
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Section | title = <h1>Server Side Software Architecture</h1> | 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>
  
−
<div class="floating_card">Our software is built on the standard LEMP (Linux, Nginx, MySQL, and PHP) architecture. The software has been designed to work on the latest LTS version of Ubuntu Linux (Server Edition).  There are 3 main components to the software application:</div>
 
  
−
{{Grid 2 | left_width = 500px | left =
+
{{Top of Page}}
−
<dl>
+
{{hr}}
−
<dt>Web Server</dt>
 
−
<dd>This makes up the bulk of the application and consists primarily of PHP web pages being served up by the Nginx web server.</dd>
 
  
−
<dt>Database</dt>
+
<center><h2>Core Application Components</h2></center>
−
<dd>The database stores all the unique, customer specific, information.</dd>
 
  
−
<dt>Media Server</dt>
 
−
<dd>This portion of the application handles all the communication with the cameras and video streams being served out to the client PCs.  It also handles all the recording and clip creation.</dd>
 
−
</dl>
 
−
}}
 
  
−
<hr>
+
<b>Web Host</b>
−
<center><h2>Single Server</h2></center>
+
*Serves the PHP-based application and user interface
 +
*Powered by the Nginx web server
  
−
From a physical or virtual server perspective the entire server side software stack can be run on a single server.
+
{{hr - 2}}
  
−
{{img - no_click | file = specific-2.jpg}}
+
<b>Database</b>
 +
*Stores all unique, customer-specific configuration and application data
 +
*Implemented using MariaDB
  
−
<hr>
+
{{hr - 2}}
−
<center><h2>Multiple Servers</h2></center>
 
  
−
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.
+
<b>Streaming Engine</b>
 +
*Manages [[Network_Requirements#Media_Server.28s.29_to_Video_Device.28s.29|communication with cameras]]
 +
*Handles [[Network_Requirements#Client_to_Application_.26_Media_Server.28s.29|video streaming to client PCs]]
 +
*Responsible for recording, storage, and clip creation
  
−
{{img - no_click | file = specific-3.jpg}}
+
 
 +
{{Top of Page}}
 +
{{hr}}
 +
 
 +
<center><h2>Logical Server Architecture</h2></center>
 +
 
 +
 
 +
The application is divided into <strong><u>two main server roles</u></strong>:
 +
 
 +
 
 +
<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}}
 +
 
 +
<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
 +
 
 +
 
 +
{{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.
 +
 
 +
 
 +
<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
 +
*Media Servers can be added incrementally to scale performance and capacity
 +
 
 +
 
 +
{{Aside - Helpful | content = This architecture provides flexibility, scalability, and efficient handling of high video workloads.}}
 +
 
 +
 
 +
{{Top of Page}}
 
}}
 
}}

Latest revision as of 11:04, 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 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


⇧ 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:Server_Side_Software_Architecture&oldid=16898"