EnviroSense

EnviroSense Server Variants

The EnviroSense server is selected according to installation scale, transmission frequency, data type, reporting requirements and the customer’s maintenance capabilities. The same system can start with a light variant and later move to a stronger architecture.

PHPC++MariaDBPostgreSQLRedisInfluxDB

How we select the backend

Device scale

The number of measuring points and reporting frequency determine the minimum server throughput.

Data character

Current readings, long-term trends and historical reports may require different database engines.

Maintenance model

The server variant must fit the IT team’s skills, backup policy and service-monitoring approach.

Integration needs

If data is to feed customer systems, backend selection includes APIs, exports and analytical queries.

PHPlight startpilots and small installations
C++efficient backendlarger networks and low latency
Redislive readsfast cache for current data
InfluxDBtime serieshistory, trends and analytics
VariantData layerCharacteristicsTypical scaleLatencySecurityDeployment model
EnviroSense PHPPHP / files or databasequick start and simple deploymentsmall installationsstandardAES-256-CBC + HMAC-SHA256hosting / simple web server
EnviroSense PHP + .soPHP + native extensionhigher performance for cryptographic operationssmall and medium deploymentslower than pure PHPAES-256-CBC + HMAC-SHA256VPS / LAMP / LEMP
EnviroSense C++ + MariaDBMariaDB / MySQLstable relational backend for private deploymentsmedium and larger installationslow locallyAES-256-CBC + HMAC-SHA256on-premise / private cloud
EnviroSense C++ + PostgreSQLPostgreSQLadvanced queries, integrations and reportingmedium and larger installationslow locallyAES-256-CBC + HMAC-SHA256on-premise / private cloud
EnviroSense C++ + RedisRedisfast cache and live views for heavy read trafficlarge live environmentsvery lowAES-256-CBC + HMAC-SHA256private cloud / dedicated infrastructure
EnviroSense C++ + InfluxDBInfluxDBtime series, history, trends and long-term analysislarge sensor networksvery lowAES-256-CBC + HMAC-SHA256private cloud / dedicated infrastructure
STARTER

PHP

  • simple installation and quick launch
  • good choice for pilots and small networks
  • low infrastructure entry threshold
  • can be expanded in a later stage
  • clear basis for device testing

Best fit: pilots, laboratories, schools and demonstration installations

HYBRID

PHP + .so

  • PHP supported by a native extension
  • more efficient cryptographic operations
  • variant for VPS and LAMP/LEMP environments
  • larger performance reserve than pure PHP
  • good balance between simplicity and scaling

Best fit: medium deployments with classic web infrastructure

RELATIONAL

C++ + MariaDB

  • native application backend
  • relational storage for data and alerts
  • predictable maintenance model
  • variant for private infrastructure
  • easier administration for teams familiar with MySQL/MariaDB

Best fit: companies and institutions with relational data infrastructure

ADVANCED

C++ + PostgreSQL

  • advanced SQL queries
  • reporting and business integrations
  • control over structure and retention
  • solid basis for operational analytics
  • variant for organisations with their own IT team

Best fit: deployments requiring reports, integrations and data control

LIVE

C++ + Redis

  • fast access to current data
  • cache for dashboards and operator views
  • high performance under many reads
  • good choice for live previews
  • can operate as a supporting layer

Best fit: systems with intensive live monitoring

TIMESERIES

C++ + InfluxDB

  • natural support for time-series data
  • trends, history and aggregations
  • efficient writes for measurement series
  • strong basis for environmental reporting
  • variant for extensive sensor networks

Best fit: long-term monitoring and trend analysis