Edge Processing vs. Infrastructure Duplication

Place only latency-sensitive workloads at shared edge platforms; retain management, analytics, and delay-tolerant processing centrally to avoid duplicating security and infrastructure.

CyberTRIZ analysis · Telecommunications contradiction NC018 · one of 8,235 worked contradictions published by CyberTRIZ.AI

Regulations

EU_NIS2 IEC_62443 ISO_27001

Business Context

Edge computing reduces latency and can improve local service responsiveness by placing processing resources closer to users and devices. However, distributing computing infrastructure across many locations can duplicate servers, storage, networking, security controls, management systems, and maintenance requirements. Centralized infrastructure improves pooling efficiency but may not satisfy latency-sensitive workloads.

Telecommunications TRIZ Resolution

Processing should be distributed selectively according to workload characteristics. Only functions that benefit materially from proximity should operate at the edge, while storage, background analytics, management, and delay-tolerant processing remain regional or centralized. Shared edge platforms can support multiple applications rather than creating dedicated infrastructure for each service.

Applicable TRIZ Principles

Principle 1 – Segmentation separates workloads according to latency and locality requirements.

Principle 5 – Merging allows multiple applications to share common edge resources.

Principle 3 – Local Quality places specialized processing only where local conditions justify it.

Expected Outcome

Lower latency for critical applications

Reduced edge infrastructure duplication

Higher computing utilization

Lower distributed operational complexity

Decision Indicators

Early indicators include:

Edge facilities contain large amounts of underused computing capacity.

Each new service introduces dedicated edge infrastructure.

Workloads are placed at the edge without measurable latency requirements.

Distributed maintenance costs increase rapidly.

Central and edge architectures are planned independently.

TRIZ principles applied

P1 SegmentationP5 MergingP3 Local quality

Controls that address this (22)

EU_NIS2-CTRL-001 - Daily safeguarding reconciliationoperational · critical priority · Daily reconciliation between safeguarded customer balances, core ledger balances and safeguarded bank accounts. Variances above EUR 100 must EU_NIS2-CTRL-002 - Critical ICT incident reportingoperational · critical priority · All major ICT incidents impacting payment services, customer data or availability must be classified within 4 hours and reported under DORA EU_NIS2-CTRL-003 - GDPR breach notification workflowoperational · critical priority · Personal data breaches must be assessed within 12 hours and reported to the Belgian DPA within 72 hours where risk to data subjects exists.