Edge Computing vs. Infrastructure Duplication
Deploy edge resources only where latency, locality, or regulatory requirements are demonstrable, and share common platforms across multiple applications.
CyberTRIZ analysis · Telecommunications contradiction TA024 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Edge computing can reduce latency, localize data processing, improve resilience, and support applications that require resources close to users. Distributing computing across many locations, however, can duplicate servers, storage, power, security, management systems, and maintenance effort. A network can therefore become more responsive while less efficient.
Telecommunications TRIZ Resolution
Edge deployment should be selective and shared. Only workloads with meaningful latency, locality, continuity, or regulatory requirements should operate at the edge, while common platforms support multiple applications. Delay-tolerant processing, data storage, and management can remain regional or centralized. Workloads can also move dynamically as demand changes.
Applicable TRIZ Principles
Principle 1 – Segmentation separates workloads according to genuine edge requirements.
Principle 5 – Merging allows multiple services to share common edge infrastructure.
Principle 15 – Dynamics adjusts workload placement according to current conditions.
Expected Outcome
Lower latency for appropriate workloads
Reduced edge infrastructure duplication
Higher resource utilization
Lower distributed operating cost
Decision Indicators
Early indicators include:
Edge infrastructure remains significantly underutilized.
Each new application creates dedicated edge resources.
Workloads are placed locally without measurable latency requirements.
Edge maintenance costs grow faster than service value.
Central and distributed computing are planned as mutually exclusive architectures.