IVS Wiki:Server Side Software Architecture: Difference between revisions

From IVS Wiki
Jump to navigation Jump to search
Created page with "{{Article - Manual | content = <h1>Server Side Software Architecture</h1> <div class="floating_card">Our software is built on the standard LEMP (Linux, Nginx, MySQL, and PHP)..."
 
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Article - Manual | content =  
{{Article - Manual | content =  
<onlyinclude>
<h1>Server Side Software Architecture</h1>
<h1>Server Side Software Architecture</h1>
<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>
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>MariaDB</strong>
*<strong>PHP</strong>
 
 
{{Top of Page}}
{{hr}}
 
{{Manual lvl 2 | title = Core Application Components | content =
 
 
<b>Web Host</b>
*Serves the PHP-based application and user interface
*Powered by the Nginx web server


{{Grid 2 | left_width = 500px | left =
<dl>
<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>
{{hr - 2}}
{{hr - 2}}
<dt>Database</dt>
 
<dd>The database stores all the unique, customer specific, information.</dd>
<b>Database</b>
*Stores all unique, customer-specific configuration and application data
*Implemented using MariaDB
 
{{hr - 2}}
{{hr - 2}}
<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>


<b>Streaming Engine</b>
*Manages communication with cameras
*Handles video streaming to client PCs
*Responsible for recording, storage, and clip creation
}}
{{Top of Page}}
{{hr}}


{{img - resize | file = VALT6_Docker_Architecture.png}}
{{Manual lvl 2 | title = Logical Server Architecture | content =  
The application is divided into two main server roles:
 
 
<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
}}
}}


<hr>
<h2>Single Server</h2>


From a physical or virtual server perspective the entire server side software stack can be run on a single server.
{{Top of Page}}
{{hr}}


{{img - no_click | file = specific-2.jpg}}
{{Manual lvl 2 | title = Deployment Models | content = }}


<hr>
{{Float | content = {{img - resize | file = Network Architecture-One Server.webp | width = 300px | style = margin:0px 10px}} }}
<h2>Multiple Servers</h2>
{{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.
}}


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.
{{hr - 2}}


{{img - no_click | file = specific-3.jpg}}
{{Float | content = {{img - resize | file = Network Architecture-Multi Server.webp | width = 300px | style = margin:0px 10px}} }}
{{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.
 
 
<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}}</onlyinclude>}}

Latest revision as of 21:50, 20 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
  • MariaDB
  • 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

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.

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://ivs.help/wiki/index.php?title=IVS_Wiki:Server_Side_Software_Architecture&oldid=17498"