Technical Specification
This section defines expected system scale parameters to support architecture planning and to avoid over-engineering scalability. The values below are not strict limits but agreed planning assumptions based on current usage and expected growth.
All architectural decisions should be validated against these assumptions. If assumptions change materially, this section must be updated.
Current State (Baseline)
- Active installations: 24
- Average users per installation: 5
- Total users: ~120
- Data generation rate:
Each installation produces 1 data point per minute
Growth Assumptions
- Installations are expected to double every year
- User count scales linearly with installations
- Data ingestion scales linearly with installations
- System is expected to support at least 3 years of growth without major architectural redesign
Target Scale Projections
Installations
| Year | Installations |
|---|---|
| Current | 24 |
| +1 year | 48 |
| +2 years | 96 |
| +3 years | 192 |
Users
Assumption: 5 users per installation
| Year | Total Users |
|---|---|
| Current | 120 |
| +1 year | 240 |
| +2 years | 480 |
| +3 years | 960 |
Concurrent (Live) Users
Assumption:
- ~10–15% of users active concurrently during peak hours
| Year | Estimated Concurrent Users |
|---|---|
| Current | 15–20 |
| +1 year | 30–40 |
| +2 years | 60–75 |
| +3 years | 120–150 |
Data Ingestion
Per Installation
- 1 data point per minute
- 60 data points per hour
- 1,440 data points per day
- 525,600 data points per year
System-wide Data Points
| Year | Installations | Data Points / Day | Data Points / Year |
|---|---|---|---|
| Current | 24 | ~34,560 | ~12.6 million |
| +1 year | 48 | ~69,120 | ~25.2 million |
| +2 years | 96 | ~138,240 | ~50.5 million |
| +3 years | 192 | ~276,480 | ~101 million |
Data Retention Assumptions
Unless stated otherwise:
- All raw data points are stored
- No automatic down-sampling or aggregation is assumed
- Historical data must remain accessible for reporting and audits
Architectural Implications (Non-binding)
Based on the above assumptions:
- The system does not require hyperscale architecture
- Single-region deployment is sufficient
- Database design must support:
- ~100 million rows over 3 years
- Append-heavy write patterns
- Time-series queries by installation and time range
- Read traffic is expected to be significantly lower than write traffic
- Peak load is driven by:
- Report generation
- Dashboard views during business hours
Out of Scope
This document does not define:
- Hard system limits
- Performance SLAs
- Disaster recovery requirements
- High-availability guarantees
These topics should be addressed separately if needed.
Revision Notes
This section reflects current expectations as of writing.
Any change in growth rate, data frequency, or retention strategy requires revisiting these assumptions.