What This Category of Data Looks Like
Data originates from ground-based financial data sources, forwarded via geostationary satellite Ka-band links as yield and market quote data. Data transmission is limited by satellite transit windows. Full daily reports are pushed at fixed times each day. High-frequency market quote sub-fields sync every 10 minutes during transit windows. Each data entry uses structured JSON format, with fields including satellite_link_id, data_collect_time, target_code, yield_basis, market_vol, and others. The unit for yield_basis is basis points. The unit for market_vol is points.
Constraints on Database and Operations Workflows
Transit-based transmission constraints for satellite communications data require databases to support mixed write modes: scheduled bulk writes and real-time incremental writes. Continuous, stable online data streams cannot be relied on. Data uses a combined identifier of satellite_link_id and data_collect_time. A composite index must be created to enable fast queries by link and time range, and to prevent cross-link data mixing. The yield_basis field uses basis point units. A high-precision numeric storage type must be configured to avoid floating-point calculation errors. Burst sync traffic from high-frequency sub-fields triggers database write peaks. A message queue must be used to buffer traffic, and prevent write timeouts during operations.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
batch_write_batch_size | 150 records/batch | Matches single-transmission data volume during satellite transit windows, and avoids database write locks from overly large single batches |
composite_index_fields | satellite_link_id, data_collect_time | Matches core query dimensions of the data, and speeds up retrieval requests by link and time range |
number_precision_type | DECIMAL(18,6) | Meets high-precision storage requirements for basis point units, and avoids numerical deviations from floating-point calculations |
traffic_queue_timeout | 300 seconds | Covers typical satellite transit window duration, buffers burst write traffic, and prevents database overload |
missing_field_retry_times | 2 retries | Addresses field loss from occasional satellite link packet loss, and balances retry overhead and data integrity |
db_write_timeout | 600 seconds | Adapts to write time required for bulk data, and avoids write task timeouts from short transit windows |
The parameter values provided on this page are general recommendations used as a starting point for configuration. Actual values are affected by data format, data volume, and business rules. Each scenario requires specific analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Configuration Errors
- Symptom: The database returns an insufficient number of query results, and historical data for some links cannot be retrieved. Cause: The
composite_index_fieldsconfiguration is not set tosatellite_link_id, data_collect_time. Queries by link skip index usage, triggering full table scans. Some data is filtered out due to scan timeouts. - Symptom: Bulk write tasks frequently time out, and write success rates are lower than expected. Cause: No reasonable
batch_write_batch_sizeis configured. Single-batch data volume exceeds the database's single-write capacity limit. Notraffic_queue_timeoutis set to buffer traffic, leading to write request backlogs and timeouts. - Symptom: The
satellite_link_idfield is empty for some data entries, making link-based classification statistics impossible. Cause: No retry logic is configured formissing_field_retry_times. Field loss from occasional satellite link packet loss is not resolved before writing to the database, leaving the field empty.
How to Confirm Configuration Is Applied Correctly
- A bulk write test using a data volume matching a transit window is executed. Database write logs are checked for timeout errors, to confirm the write configuration aligns with current business traffic.
- A query request filtered by
satellite_link_idand time range is submitted. Query response times are checked against expected thresholds, to confirm the composite index configuration is active. - A satellite link packet loss scenario is simulated, and test data missing the
satellite_link_idfield is created. The retry logic is verified to trigger, and the field is completed prior to writing, to confirm the missing field retry configuration is active. - The storage type configuration for the
yield_basisfield is reviewed. A high-precision numeric type is confirmed to be set. Historical stored data is checked for precision deviations, to confirm the numeric storage configuration is active.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.