Telecommunications

Network Infrastructure on Legacy Foundations

Carriers running billing, provisioning, and network management on systems designed before smartphones existed. 5G on top of 1990s OSS/BSS.

Key data points

Enterprise JavaScript in telecom

Telecom web properties lean heavily on enterprise JavaScript frameworks. Angular is the carrier pattern. Source: WebPulse scan.

Angular 14% (Korea), 9% (Thailand)

Annual telecom IT spending on maintenance

Of total IT budget consumed by keeping legacy running. 30% left for innovation.

~70%

Customer churn cost from system failures

Billing errors, provisioning delays, service activation failures — all legacy system symptoms.

$2.5B globally/yr

5G services requiring legacy integration

New 5G capabilities constrained by legacy billing and provisioning backends.

~85%

Average telecom digital transformation timeline

Among the longest of any industry. Complexity of legacy interconnections.

5-8 years

Risk factors

What keeps Telecommunications CISOs awake

●

OSS/BSS platforms from the 1990s-2000s managing billions in revenue with no modern API layer

●

Billing systems processing millions of transactions daily on COBOL and mainframe backends

●

Network provisioning locked to vendor-specific legacy interfaces — Ericsson, Nokia, Huawei proprietary stacks

●

Customer data across dozens of siloed legacy systems with no unified view

●

5G rollout constrained by legacy backend limitations — modern radio on ancient billing

Stack comparison

Typical vs Recommended

Typical Telecommunications stack

Java 8 31

Oracle Database 40

COBOL 8

.NET Framework (4.x) 39

IIS 35

Recommended modern stack

Java 17+ 70

PostgreSQL 81

Kubernetes 71

FastAPI 80

React 73

Score your own stack →

Regulatory landscape

Compliance Exposure

GDPR / Data Privacy

Subscriber data across legacy systems creates compliance blind spots. Data subject requests require querying dozens of siloed databases.

Network Security (NIS2)

EU directive classifying telecoms as essential entities. Legacy infrastructure security posture under direct regulatory scrutiny.

Lawful Intercept

Legal interception requirements on legacy switching infrastructure. Compliance complexity multiplied by system age.

Number Portability

Regulatory requirements met through legacy database integrations. Migration risk affects regulatory compliance.

Latest Telecommunications insights

Business Efficiency

Network Infrastructure on Legacy Foundations

What keeps Telecommunications CISOs awake

Typical vs Recommended

Compliance Exposure

The Vendor Lock: When Your Infrastructure Belongs to Someone Else

AI Can't Talk to Your Legacy Systems. That's About to Be a Problem.

COBOL, Java 8, Python 2: The Three Horsemen of Legacy

The Legacy Iceberg: What's Below the Waterline

The Global Framework Map: Where Legacy Is Most Entrenched

The WordPress Talent Crisis: Shrinking Supply, Rising Costs, Declining Skills