Device scale
The number of measuring points and reporting frequency determine the minimum server throughput.
EnviroSense
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.
The number of measuring points and reporting frequency determine the minimum server throughput.
Current readings, long-term trends and historical reports may require different database engines.
The server variant must fit the IT team’s skills, backup policy and service-monitoring approach.
If data is to feed customer systems, backend selection includes APIs, exports and analytical queries.
| Variant | Data layer | Characteristics | Typical scale | Latency | Security | Deployment model |
|---|---|---|---|---|---|---|
| EnviroSense PHP | PHP / files or database | quick start and simple deployment | small installations | standard | AES-256-CBC + HMAC-SHA256 | hosting / simple web server |
| EnviroSense PHP + .so | PHP + native extension | higher performance for cryptographic operations | small and medium deployments | lower than pure PHP | AES-256-CBC + HMAC-SHA256 | VPS / LAMP / LEMP |
| EnviroSense C++ + MariaDB | MariaDB / MySQL | stable relational backend for private deployments | medium and larger installations | low locally | AES-256-CBC + HMAC-SHA256 | on-premise / private cloud |
| EnviroSense C++ + PostgreSQL | PostgreSQL | advanced queries, integrations and reporting | medium and larger installations | low locally | AES-256-CBC + HMAC-SHA256 | on-premise / private cloud |
| EnviroSense C++ + Redis | Redis | fast cache and live views for heavy read traffic | large live environments | very low | AES-256-CBC + HMAC-SHA256 | private cloud / dedicated infrastructure |
| EnviroSense C++ + InfluxDB | InfluxDB | time series, history, trends and long-term analysis | large sensor networks | very low | AES-256-CBC + HMAC-SHA256 | private cloud / dedicated infrastructure |
Best fit: pilots, laboratories, schools and demonstration installations
Best fit: medium deployments with classic web infrastructure
Best fit: companies and institutions with relational data infrastructure
Best fit: deployments requiring reports, integrations and data control
Best fit: systems with intensive live monitoring
Best fit: long-term monitoring and trend analysis