Satellite networks are operational now and deliver connectivity globally, including to places where traditional infrastructure is difficult or impossible. In that setup, space is becoming another network edge rather than a replacement for terrestrial infrastructure.
Orbital compute stays constrained
Mike Hicks, principal solutions analyst at Cisco ThousandEyes, says future orbital compute may add new processing and storage capabilities. He also says space-based compute will likely be smaller and more specialized than hyperscale infrastructure on Earth because launch capacity, radiation, power generation, cooling, and physical size all limit what can run in orbit.
That is a narrower brief than the cloud model that came before it. Content delivery networks moved content closer to users, cloud platforms added elasticity and geographic redundancy, and edge computing pushed processing toward the point of data creation.
Why the workload split matters
The same analysis points to satellite-based Earth observation as a concrete use case: large imagery and sensor datasets could be partially processed in orbit to reduce bandwidth needs and speed up insights. Other possible uses include distributing cached content, supporting remote connectivity, and serving ships, aircraft, and industrial operations.
Satellite constellations are dynamic and require constant handoffs between spacecraft and ground stations. A low-Earth orbit satellite round trip of 20 to 40 milliseconds is still not equivalent to terrestrial fiber latency, and satellite connectivity is often asymmetric, with more capacity for downloads than for upstream traffic.
What service architects have to design around
Large uplink transfers are more expensive than equivalent terrestrial transfers because of power constraints and radio transmission requirements. That is why not every workload belongs in space, even if the orbital layer keeps expanding.
For service architects, the practical question is which parts of a service should run on terrestrial fiber, subsea cable systems, wireless access networks, hyperscale cloud environments, edge compute platforms, or satellite constellations. Hicks says future space-based compute infrastructure may still be years away from large-scale deployment, but the design questions are already here.
What this means for cloud and edge teams
Cloud, edge, and network teams will have to treat satellite connectivity as part of the service path, not an exception. The constraints are different, but the architecture problem is familiar: place workloads where they fit, then make the path between them work.