← Back to the chapter · Next detail →
Technical detail · Cloud Data: Platforms and Services
Fleet telemetry sizing
The delivery-fleet example sizes a different workload before comparing prices: 10,000 delivery vehicles report every 30 seconds, with 200 bytes per message, for 12 hours/day and 26 days/month.
| Quantity | Calculation | Result |
|---|---|---|
| Messages per vehicle per day | 12 hours × 60 minutes/hour × 2 messages/minute | 1,440 messages |
| Daily message count | 10,000 × 1,440 | 14,400,000 messages/day |
| Monthly message count | 14,400,000 × 26 | 374,400,000 messages/month |
| Daily data volume | 14,400,000 × 200 bytes | 2,880,000,000 bytes = 2.88 GB/day |
| Monthly data volume | 2.88 GB/day × 26 | 74.88 GB/month |
| 90-day raw retention, approximated as three modeled months | 74.88 GB/month × 3 | 224.64 GB |
| Two-year aggregate retention at 10:1 compression | 74.88 GB/month × 24 / 10 | 179.712 GB |
| Example messaging charge at a contracted $0.80 per million messages | 374.4 million × $0.80 | $299.52/month |
The message charge is only one line item. The platform choice must also account for identity integration, stream processing, map or route services, dashboards, storage lifecycle, monitoring, support, and operating effort. These calculations expose the assumptions that a headline message price leaves out.