Skip to main content
Back to News & insights
Network design[Publication date required]

Terrestrial and satellite connectivity are complements, not rivals

The useful question is not which technology wins. It is which layer carries which obligation — and what happens to the site when the primary path fails.

Discussions about satellite connectivity often get framed as a contest with terrestrial infrastructure. That framing is not useful to anyone who has to design a network. Fibre and satellite have different cost curves, different deployment timelines and different failure modes, and a competent design uses those differences deliberately.

Where each layer earns its place

Terrestrial infrastructure remains the right answer wherever it can reach economically. Capacity is high, incremental cost per bit is low, and the physics are forgiving. The constraint is reach: fibre economics depend on route density and on the time it takes to build, and both are challenging across dispersed or difficult terrain.

Satellite and advanced connectivity earn their place precisely where those constraints bite — remote sites, dispersed operations, locations chosen for a project rather than for network availability, and situations where the requirement exists now and a terrestrial build does not.

The design question

For a site with a genuine continuity obligation, the question is not which technology to select but which layer carries which obligation. A common structure looks like this:

  • Terrestrial as primary where available, carrying bulk capacity
  • Satellite as a diverse backup path with genuinely independent failure modes
  • Failover behaviour defined, configured and tested — not assumed
  • Clarity about which applications must continue on the backup path, and at what performance

That last point is where most designs are weakest. A backup path that carries a fraction of primary capacity is still valuable, but only if someone has decided in advance what runs across it. Discovering that during an outage is expensive.

Deployment is the harder half

In practice, the technology choice is rarely the binding constraint. The binding constraints are import flow, secure storage, site survey quality, installation standards, and whether anyone can reach the site quickly when something fails. A well-chosen technology deployed poorly performs worse than a compromise deployed properly.

  • Satellite
  • Fibre
  • Resilience
  • Remote sites
  • Design

Proposed capabilityA perspective article by Taurus Arm on network design. It does not describe any specific product, provider or commercial arrangement.

Discuss any of this in more detail

If a question here is relevant to a programme you are planning, we are glad to go deeper — including on the parts where the honest answer is that it depends.