Architecture Fundamentals

Flopsar consists of three components:

• Agent

• Server

• Workstation

Workstation as a web application, can be served from either the server directly or any web server, which is able to operate as a reverse proxy.

Standalone Architecture

In the standalone architecture, the Flopsar server includes an embedded HTTP server that serves the Workstation application directly. This configuration simplifies the deployment process by eliminating the need for users to set up an additional reverse proxy server.

Key Features:

1. Integrated HTTP Server:

   • The built-in HTTP server is capable of handling all incoming HTTP requests, serving both the Workstation web interface and the collected data. This self-contained setup ensures that the server is immediately ready to use after installation, without requiring complex networking configurations.

2. Simplified Setup:

   • Since the server directly serves the Workstation application, there is no need for external reverse proxies or additional software components. This reduces the complexity and potential points of failure, making it easier for users to get started with Flopsar.

3. Ideal for Small Deployments:

   • The standalone architecture is ideal for smaller environments or development setups where ease of use and minimal configuration are priorities. It provides a straightforward way to explore and utilize Flopsar without the overhead of managing multiple servers or services.

In summary, the standalone architecture offers a convenient, all-in-one solution for deploying Flopsar, making it accessible and user-friendly, especially for those who prefer a minimalistic approach to setup and configuration.

Reverse Proxy Architecture

In an alternative configuration, the Workstation web application is served from a separate HTTP server, which also functions as a reverse proxy. This server handles the web application's static assets and redirects all data requests to the Flopsar server.

Key Features:

1. Separation of Concerns:

   • By serving the Workstation application from a separate HTTP server, this architecture decouples the user interface from the data-processing backend.

2. Reverse Proxy Functionality:

   • The HTTP server acts as a reverse proxy, forwarding all requests for data to the Flopsar server. This configuration can improve security and performance by isolating the Flopsar server from direct access, allowing for more granular control over request handling and access permissions.

3. Enhanced Flexibility:

   • This architecture is suitable for larger or more complex environments, where there is a need for increased flexibility and control.

4. Improved Security:

   • Using a reverse proxy server can enhance security by acting as a barrier between the internet and the Flopsar server. It allows administrators to implement security measures such as IP whitelisting, rate limiting, and request filtering before traffic reaches the Flopsar server.

In summary, the reverse proxy architecture offers an advanced deployment option that provides greater flexibility, scalability, and security, making it ideal for production environments where these factors are a priority.