The cardinality wall: The hidden data bottleneck for LEO constellations

2026-05-20 · Source: SpaceNews · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure, Data Science & Analytics · Depth: Advanced, medium

Summary

The LEO satellite industry faces a "cardinality wall," a critical data bottleneck stemming from the immense volume and complexity of telemetry generated by thousands of spacecraft. Traditional ground systems, built for smaller missions, struggle with millions of distinct telemetry streams per second, each with extensive metadata like spacecraft ID and mission phase. Relational databases and log analytics platforms fail due to heavy indexing, poor handling of continuous, high-velocity writes, and inefficient time-based querying. This problem intensifies with long-term data retention needs for investigations and predictive modeling. Loft Orbital, managing over 500 million telemetry measurements daily, successfully transitioned to a time series-oriented architecture to overcome these limitations, highlighting the necessity of preserving full data context for operational visibility and mission resilience.

Key takeaway

For AI Architects and MLOps Engineers designing LEO ground systems, relying on traditional relational databases for telemetry will create critical bottlenecks. You must prioritize architectures that handle high-cardinality, continuous data streams and support long-term retention without sacrificing context. Decouple ingestion from analytics and adopt time series-oriented solutions to ensure mission resilience and enable robust predictive modeling, avoiding costly operational blind spots.

Key insights

The exponential growth of LEO satellite telemetry creates a "cardinality wall" that breaks traditional ground system architectures, demanding new distributed approaches.

Principles

• Telemetry is a distributed systems problem.
• Context preservation is critical for operations.
• Incremental scaling fails at high cardinality.

Method

Recognize architectural strain, identify cardinality impact points, decouple telemetry pipeline components (e.g., ingestion from analytics), and prioritize full context preservation over data reduction.

In practice

• Decouple high-throughput ingestion.
• Avoid downsampling or stripping metadata.
• Revisit systems assuming sequential ingestion.

Topics

• LEO Constellations
• Satellite Telemetry
• High Cardinality Data
• Ground Systems Architecture
• Time Series Databases
• Distributed Systems

Best for: CTO, VP of Engineering/Data, Data Engineer, AI Architect, MLOps Engineer

Related on AIssential

• Free-Placement Optimization of Ground Station Locations for Low-Earth Orbit Satellites — SCORE optimizes LEO ground station placement via sequential refinement, outperforming fixed-site and differential evolution methods.
• What Your Git History Is Trying to Tell You — Data-driven visibility into engineering pipelines reveals hidden bottlenecks and enables targeted process improvements.
• The Orbital Data Center Hype Machine Is Already in Orbit — Orbital data centers face immense technical and logistical hurdles, making Elon Musk's aggressive timelines for cost-effectiveness highly improbable.
• Startup challenging satellite industry’s multi-orbit playbook — Contrivian argues multi-orbit satellite systems degrade performance; multiple LEO constellations offer superior, consistent latency for critical applications.
• Your Data is Made Powerful By Context (so stop destroying it already) (xpost) — The "three pillars" observability model destroys data context, hindering AI agent validation and making data exponentially less powerful.
• The Hardware Bottleneck AI Can’t Fix — Hardware engineering's lack of software-like tooling creates a bottleneck, hindering AI's impact and requiring specialized data platforms.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by SpaceNews.