Competition Law And Governance Of Resilience Architectures

Competition Law and Governance of Resilience Architectures

1. Introduction

Resilience architectures refer to market structures designed to remain functional despite shocks, failures, supply disruptions, cyber incidents, technological changes, financial stress, or the exit of an important participant. In competition law, the concept becomes important where resilience depends upon multiple suppliers, interoperability, alternative distribution channels, data portability, multi-homing, switching possibilities, redundant infrastructure, and contestable markets.

Competition law traditionally focuses on preventing conduct that reduces competition. Increasingly, however, competition authorities also examine whether a market has become so dependent on a single undertaking, platform, infrastructure, technology, dataset, or distribution channel that competitors cannot effectively challenge it.

Thus, the relationship may be expressed as:

Competition → diversity of market participants → redundancy and alternatives → resilience.

A resilient competitive market is not necessarily one with many firms at all times. Rather, it is one in which credible alternatives can emerge, expand, interoperate and replace an incumbent when circumstances change.

2. Meaning of Resilience Architectures in Competition Law

A resilience architecture can contain several layers.

A. Supplier resilience

A market is more resilient when customers can switch between several suppliers rather than depending upon one dominant supplier.

Examples:

  • semiconductor suppliers;
  • cloud providers;
  • energy suppliers;
  • logistics providers;
  • payment networks;
  • telecommunications operators.

B. Infrastructure resilience

Essential infrastructure should not become a bottleneck through which competitors must pass.

Examples include:

  • telecommunications networks;
  • payment infrastructure;
  • cloud infrastructure;
  • app stores;
  • digital identity systems;
  • railway infrastructure;
  • electricity grids.

C. Technological resilience

Interoperability allows alternative technologies to operate alongside one another.

This is particularly important where:

  • proprietary standards dominate;
  • APIs are controlled by one firm;
  • software is vertically integrated with hardware;
  • platforms determine compatibility;
  • switching requires substantial technical migration.

D. Distribution resilience

A competitive market becomes fragile if one undertaking controls the principal route by which rivals reach consumers.

Examples include:

  • search engines;
  • app stores;
  • marketplaces;
  • social-media platforms;
  • online advertising;
  • payment gateways.

E. Data resilience

Data can function as a strategic competitive input. A market may become less resilient when an incumbent accumulates data that competitors cannot replicate and simultaneously prevents data portability or access.

F. Financial and organizational resilience

Competition can also be affected by:

  • exclusive contracts;
  • loyalty rebates;
  • long-term supply agreements;
  • acquisition of potential competitors;
  • vertical integration;
  • cross-subsidization;
  • capacity reservation.

3. Competition Law Framework

Resilience architectures are not normally a separate statutory category of competition law. They are examined through established doctrines.

3.1 Abuse of Dominant Position

A dominant undertaking may violate competition law when it uses control over an important infrastructure or input to exclude competitors.

Typical conduct includes:

  • refusal to supply;
  • discriminatory access;
  • margin squeeze;
  • exclusive dealing;
  • loyalty rebates;
  • tying;
  • self-preferencing;
  • interoperability restrictions;
  • discriminatory technical standards.

Under EU law, Article 102 TFEU prohibits abusive conduct by dominant undertakings, including exclusionary conduct. The European Commission's 2026 Article 102 Guidelines expressly address exclusionary abuses and are intended to increase consistency in enforcement.

4. Essential Facilities and Resilience

The essential-facilities principle is particularly relevant.

Where a competitor depends upon infrastructure controlled by a dominant undertaking, competition law may require access in exceptional circumstances.

However, competition law does not automatically require every dominant undertaking to share every facility.

The central questions generally include:

  1. Is the facility indispensable?
  2. Can competitors realistically duplicate it?
  3. Is access necessary for effective competition?
  4. Would refusal eliminate effective competition?
  5. Is there an objective justification?
  6. Would compulsory access undermine investment incentives?

The doctrine therefore attempts to balance:

competitive resilience
against
incentives to invest in infrastructure.

5. Interoperability as a Resilience Mechanism

Interoperability is one of the most important mechanisms for creating resilient competition.

If two systems are interoperable:

System A ↔ System B ↔ System C

customers can move between providers without rebuilding their entire technological environment.

Without interoperability:

Dominant system → proprietary interface → switching costs → customer lock-in → weaker competitive entry

This is particularly significant in:

  • cloud computing;
  • enterprise software;
  • operating systems;
  • telecommunications;
  • payment systems;
  • automotive software;
  • IoT;
  • AI infrastructure.

6. Case Laws

Case 1: United States v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001)

Facts

Microsoft possessed substantial power in the market for Intel-compatible PC operating systems. The case concerned Microsoft's conduct toward competing technologies, particularly Netscape's browser and Java.

Legal significance

The D.C. Circuit considered Microsoft's use of contractual and technological mechanisms to protect its operating-system monopoly.

The case demonstrated that competition concerns may arise where a dominant technological architecture is used to prevent alternative platforms or technologies from developing.

Resilience principle

A technology ecosystem becomes less resilient when the dominant architecture prevents competing technologies from obtaining sufficient scale.

The case therefore illustrates:

Technological openness can be important to preserving competitive alternatives.

7. Case 2: Microsoft Corp. v. Commission, T-201/04

The EU Microsoft case concerned Microsoft's refusal to provide interoperability information to competing work-group server operating-system developers.

The General Court recognized the significance of interoperability for maintaining viable competition. The remedy required disclosure of interoperability information sufficient to permit competing operating systems to interoperate with Microsoft's dominant architecture.

Importance for resilience

This is one of the clearest examples of competition law being used to preserve an interoperable ecosystem.

Without interoperability:

Dominant platform → compatibility advantage → reduced viability of rivals → fewer alternatives.

With interoperability:

Common technical interaction → greater substitutability → rival entry → greater system resilience.

8. Case 3: Bronner v. Mediaprint, C-7/97

Facts

Bronner concerned access to a newspaper distribution system operated by established competitors.

The Court of Justice considered when refusal to provide access to an infrastructure could constitute abuse of dominance.

Legal principle

The Court adopted a demanding approach to compulsory access. The infrastructure had to be indispensable, in the sense that there was no actual or potential substitute.

Resilience significance

The case establishes an important limit:

Competition law should not automatically convert every commercially valuable asset into shared infrastructure.

Otherwise, firms may have weaker incentives to build resilient infrastructure in the first place.

Therefore, resilience governance must preserve both:

  • access for competitive alternatives, and
  • investment incentives for infrastructure owners.

9. Case 4: Slovak Telekom v. Commission, C-165/19 P

The case concerned broadband infrastructure and access to Slovak Telekom's local-loop network.

The Court dealt with Article 102 TFEU, regulatory access obligations and the conditions imposed by the incumbent on competing operators.

Competition principle

The case illustrates how control over telecommunications infrastructure can give an incumbent the ability to affect downstream competition.

Resilience principle

Telecommunications systems are inherently infrastructure-dependent.

If competing operators cannot obtain viable access:

Infrastructure control → reduced downstream competition → fewer independent networks/services → systemic vulnerability.

The case therefore demonstrates the connection between:

  • access;
  • pricing;
  • infrastructure;
  • entry;
  • downstream competition.

10. Case 5: Intel Corp. v. Commission, C-413/14 P

Facts

Intel was accused of using rebates to exclude AMD from the x86 CPU market.

The European Commission had imposed a €1.06 billion fine. The Court of Justice set aside the General Court judgment and required examination of Intel's arguments concerning the ability of the rebates to restrict competition.

Resilience significance

Exclusive or loyalty-inducing arrangements can make a supply chain dependent on one undertaking even where alternative suppliers technically exist.

For resilience analysis, the relevant concern is therefore not merely:

"Does another supplier exist?"

but also:

"Can that supplier realistically reach sufficient customers to remain an effective competitive constraint?"

Principle

Nominal alternatives are not necessarily resilient alternatives.

A competitor that is contractually or economically foreclosed may exist in theory while being unable to provide meaningful redundancy.

11. Case 6: Google Android, T-604/18 and C-738/22 P

Google's Android ecosystem involved:

  • Google Search;
  • Chrome;
  • Play Store;
  • Android operating systems;
  • device manufacturers;
  • mobile network operators.

The General Court largely upheld the Commission's findings concerning restrictions involving app and search distribution, exclusivity payments and anti-fragmentation obligations.

The Court of Justice subsequently issued its judgment in the appeal on 2 July 2026.

Resilience significance

The case demonstrates how several layers of an ecosystem can reinforce each other:

Operating system
↓
App store
↓
Search
↓
User data
↓
Advertising
↓
Developer incentives

When these layers become mutually reinforcing, competing ecosystems may face difficulty achieving sufficient scale.

Resilience lesson

Competition analysis must therefore examine ecosystem architecture, not simply individual products.

12. Case 7: Google Shopping

In 2017, the European Commission found that Google had abused its dominant position in general search by giving prominent placement to its own comparison-shopping service while demoting competing comparison-shopping services.

Resilience significance

Search traffic was an important competitive input for comparison-shopping services.

Consequently:

Search infrastructure → traffic allocation → visibility → users → retailers → data → further scale

A dominant intermediary can therefore influence whether alternative ecosystems obtain the scale necessary to survive.

Principle

Competition governance should examine control over gateways, not merely ownership of final products.

13. Case 8: Facebook/Meta – Giphy

The UK's Competition and Markets Authority examined Meta's acquisition of Giphy.

The CMA concluded that the acquisition could reduce competition between social-media platforms because Meta could restrict competitors' access to Giphy's GIF library. It also concluded that Giphy had represented a potential challenger in digital advertising. The CMA ultimately required divestiture. The Competition Appeal Tribunal upheld the CMA's decision on five of the six challenged grounds, including its assessment concerning dynamic competition.

Resilience significance

Giphy functioned as an input for multiple social-media platforms.

The concern can be represented as:

Independent content/input provider
↓ acquisition
Platform-controlled input
↓
Potential discriminatory access
↓
Reduced alternatives

The case illustrates the importance of maintaining independent nodes within digital ecosystems.

14. Case 9: Broadcom/VMware

This is particularly relevant to resilience architectures.

In 2023, the European Commission conditionally approved Broadcom's acquisition of VMware after an in-depth investigation.

One concern involved the possibility that VMware's virtualization software could be used to degrade interoperability with rival hardware, particularly Marvell's competing hardware. The Commission accepted interoperability commitments designed to ensure comparable interoperability.

Resilience significance

This demonstrates a modern competition-law approach:

Merger control can preserve technological redundancy by protecting interoperability.

Instead of prohibiting the transaction outright, the Commission used a targeted interoperability remedy.

This is particularly important for:

  • cloud infrastructure;
  • virtualization;
  • data centres;
  • enterprise software;
  • hardware ecosystems.

15. Case 10: Amazon Marketplace

The European Commission investigated Amazon's use of non-public seller data and its Buy Box/Prime-related practices.

Amazon offered commitments addressing concerns concerning the use of non-public seller data and discriminatory treatment of competing sellers, including in relation to fulfilment and carrier conditions.

Resilience significance

Marketplace resilience depends upon independent sellers remaining capable of competing with the platform's own retail operations.

If the platform can simultaneously:

  1. operate the marketplace;
  2. observe competitors' data;
  3. control visibility;
  4. control fulfilment;
  5. operate its own retail business,

the marketplace may develop a structural dependency on the platform.

Thus, governance can require:

  • non-discriminatory access;
  • data-use restrictions;
  • transparent selection criteria;
  • freedom of logistics choice.

16. Google Search – United States

The U.S. Google search litigation provides another example of resilience-oriented remedies.

In 2024, the District Court found Google liable under Section 2 of the Sherman Act for maintaining monopolies in general search services and general search text advertising through exclusionary distribution agreements. In 2025, the court imposed remedies involving restrictions on exclusive distribution agreements and requirements concerning certain search data and syndication services.

Resilience significance

The case demonstrates that competitive resilience can depend upon whether rivals can obtain:

  • distribution;
  • user queries;
  • data;
  • scale;
  • advertising access.

The underlying structural problem can be represented as:

Exclusivity → distribution foreclosure → inadequate rival scale → weaker competition → greater dependence on incumbent.

17. Core Competition Concerns Created by Resilience Architectures

17.1 Single-source dependency

Where customers depend on one supplier, the supplier may acquire substantial bargaining power.

Potential concerns include:

  • excessive pricing;
  • discriminatory terms;
  • supply restrictions;
  • foreclosure;
  • degraded quality.

17.2 Single-platform dependency

Digital businesses may depend on:

  • app stores;
  • search engines;
  • marketplaces;
  • payment platforms;
  • social networks.

Competition law therefore increasingly considers platform dependency.

17.3 Interoperability foreclosure

A dominant firm may make competing systems technically inferior by:

  • withholding APIs;
  • delaying certification;
  • changing protocols;
  • limiting data access;
  • degrading compatibility.

The Microsoft and Broadcom/VMware matters demonstrate why interoperability can become a competition-law remedy.

18. Network Effects and Resilience

Network effects can make resilience difficult.

Suppose Platform A has 90% of users.

More users produce:

more data → better service → more users → more developers → more complementary services → still more users.

This creates a positive feedback loop.

A competitor may therefore face a scale barrier, even if it possesses a technically superior product.

Competition law consequently needs to examine:

  • network effects;
  • economies of scale;
  • switching costs;
  • data advantages;
  • interoperability;
  • multi-homing;
  • access to distribution.

19. Multi-Homing as a Resilience Mechanism

Multi-homing means users or businesses use several competing platforms simultaneously.

Example:

Seller → Amazon + Walmart Marketplace + independent website.

This provides redundancy.

If one platform changes:

  • commission rates;
  • ranking algorithms;
  • access conditions;
  • fulfilment requirements;

the seller retains alternatives.

Competition concerns arise where dominant platforms use contractual or technical restrictions to prevent multi-homing.

20. Switching Costs and Lock-In

High switching costs can undermine resilience.

Switching costs may include:

  • migration expenses;
  • loss of historical data;
  • retraining;
  • incompatibility;
  • contractual penalties;
  • loss of reputation;
  • loss of accumulated platform ratings;
  • technical redevelopment.

Competition authorities may therefore consider portability and interoperability as mechanisms that lower artificial switching barriers.

21. Data Portability and Competitive Resilience

Data portability can create competitive redundancy.

For example:

Provider A → portable data → Provider B

rather than:

Provider A → proprietary data → customer lock-in.

However, data access also raises legitimate concerns involving:

  • privacy;
  • cybersecurity;
  • trade secrets;
  • intellectual property;
  • confidential business information.

Therefore, competition remedies must be appropriately targeted.

22. Resilience and Merger Control

Merger control is particularly important because acquisitions can eliminate redundancy before a market becomes visibly concentrated.

Important questions include:

  1. Is the target an existing competitor?
  2. Is it a potential competitor?
  3. Does it provide a critical input?
  4. Does it control important data?
  5. Does it provide interoperability?
  6. Could it become a future challenger?
  7. Does the transaction create vertical foreclosure?
  8. Does it remove an independent node from the ecosystem?

The Meta/Giphy decision demonstrates how merger control can protect dynamic competition and potential competition.

23. Resilience and Vertical Integration

Vertical integration can have legitimate efficiencies.

For example:

manufacturer + distributor

may produce:

  • lower costs;
  • better coordination;
  • improved quality;
  • faster innovation.

But it can also create foreclosure incentives.

A vertically integrated firm may:

  • deny competitors inputs;
  • discriminate in access;
  • favour its own downstream business;
  • raise rivals' costs;
  • manipulate interoperability.

Therefore, competition analysis should distinguish efficiency-enhancing integration from exclusionary foreclosure.

24. Resilience and Essential Infrastructure

Important infrastructure sectors include:

Energy

  • electricity grids;
  • gas networks;
  • hydrogen infrastructure;
  • charging infrastructure.

Telecommunications

  • fibre networks;
  • mobile networks;
  • spectrum-related infrastructure;
  • internet exchanges.

Digital infrastructure

  • cloud computing;
  • data centres;
  • app stores;
  • operating systems.

Transport

  • ports;
  • rail networks;
  • airports;
  • logistics networks.

Financial infrastructure

  • payment systems;
  • card networks;
  • clearing systems.

Competition law can become an important mechanism for preventing these systems from becoming competitive bottlenecks.

25. Resilience and Supply-Chain Competition

Supply-chain resilience has two dimensions.

Efficiency model

A company may prefer:

one supplier + very low cost.

Resilience model

A company may prefer:

several suppliers + slightly higher cost + lower disruption risk.

Competition law should not automatically require firms to maintain inefficient redundancy.

Instead, it should examine whether dominant firms artificially prevent alternative suppliers from developing.

This distinction is crucial.

26. Resilience Architecture and Cartels

Resilience does not justify coordination between competitors.

Competitors might attempt to create "resilience agreements" involving:

  • common suppliers;
  • shared capacity;
  • production allocation;
  • common inventories;
  • information exchange.

Some forms of cooperation may be legitimate, particularly during emergencies, but agreements involving:

  • price fixing;
  • market allocation;
  • output restrictions;
  • customer allocation,

can constitute cartel conduct.

Therefore:

Resilience is not a blanket defence to cartel behaviour.

The competitive effects and applicable exemptions must be examined carefully.

27. Algorithmic Resilience

Modern resilience architectures increasingly rely upon algorithms.

Algorithms may control:

  • prices;
  • inventory;
  • supply allocation;
  • traffic;
  • energy distribution;
  • advertising;
  • logistics;
  • credit;
  • recommendation.

Competition risks include:

  • algorithmic collusion;
  • coordinated pricing;
  • discriminatory access;
  • automated exclusion;
  • self-preferencing;
  • algorithmic foreclosure.

Competition governance therefore needs access to:

  • model documentation;
  • audit logs;
  • input data;
  • decision rules;
  • testing records;
  • change histories.

28. Artificial Intelligence and Resilience

AI may increase both resilience and concentration.

Resilience-enhancing effects

AI can enable:

  • predictive maintenance;
  • demand forecasting;
  • supply diversification;
  • automated fault detection;
  • cybersecurity;
  • capacity optimization.

Competition risks

AI may simultaneously reinforce:

  • data advantages;
  • compute concentration;
  • cloud dependence;
  • model concentration;
  • proprietary interfaces;
  • distribution bottlenecks.

Thus:

AI resilience must be distinguished from AI-driven concentration.

29. Remedies for Resilience Problems

Competition authorities have several possible remedies.

Structural remedies

Examples:

  • divestiture;
  • separation of business units;
  • asset sales;
  • prohibition of acquisitions.

Meta/Giphy illustrates the use of divestiture to address identified merger concerns.

Behavioural remedies

Examples:

  • non-discrimination;
  • interoperability;
  • access obligations;
  • data-use restrictions;
  • transparency;
  • non-exclusive contracts.

Technical remedies

Examples:

  • API access;
  • interoperability protocols;
  • data portability;
  • technical certification;
  • open standards.

Governance remedies

Examples:

  • independent monitoring;
  • compliance officers;
  • audit rights;
  • reporting requirements;
  • algorithmic audits.

30. Key Principles Emerging from the Case Law

Resilience problemCompetition-law response
Single infrastructure bottleneckAccess regulation / essential-facility analysis
Proprietary interoperabilityInteroperability remedies
Exclusive distributionAbuse-of-dominance analysis
Loyalty rebatesEffects-based assessment
Platform self-preferencingAbuse / digital-platform regulation
Acquisition of potential rivalMerger control
Data foreclosureData-access or data-use remedies
Switching barriersPortability/interoperability
Vertical foreclosureArticle 102 / merger analysis
Network-effect concentrationEcosystem and entry analysis
Critical supplier dependencyForeclosure and exclusion analysis
Platform-controlled inputVertical/ecosystem foreclosure analysis

31. Governance Model for Resilience Architectures

A comprehensive competition-law governance framework can be structured as follows:

Stage 1 — Identify critical nodes

Determine which firms control:

  • infrastructure;
  • data;
  • standards;
  • distribution;
  • interfaces;
  • payment systems;
  • essential inputs.

Stage 2 — Identify dependencies

Ask:

Who cannot operate without whom?

Stage 3 — Measure substitutability

Examine:

  • alternative suppliers;
  • alternative technologies;
  • alternative platforms;
  • switching costs;
  • capacity constraints.

Stage 4 — Test foreclosure

Investigate:

  • exclusivity;
  • tying;
  • bundling;
  • discrimination;
  • refusal to deal;
  • self-preferencing;
  • interoperability degradation.

Stage 5 — Evaluate efficiencies

Consider:

  • cost savings;
  • quality improvements;
  • innovation;
  • security;
  • reliability.

Stage 6 — Select proportionate remedy

Possible remedies range from:

transparency → access → interoperability → non-discrimination → structural separation → divestiture.

32. Important Distinction: Resilience ≠ Redundancy

Competition law should not assume that having more firms automatically creates resilience.

For example:

20 small firms dependent on one platform

may be less resilient than:

5 independent firms with interoperable systems.

Therefore, the relevant concept is competitive redundancy, not simply numerical plurality.

33. Resilience ≠ Market Fragmentation

Excessive fragmentation can also reduce:

  • economies of scale;
  • investment;
  • innovation;
  • network quality.

Competition law therefore seeks effective competitive alternatives, rather than fragmentation for its own sake.

34. Relationship Between Competition, Innovation and Resilience

A useful conceptual chain is:

Competition

↓

Contestability

↓

Investment in alternative technologies

↓

Interoperability and substitutability

↓

Multiple competitive pathways

↓

Reduced dependency

↓

Market resilience

This is why cases such as Microsoft, Google Android, Broadcom/VMware, Meta/Giphy and Google Search are useful when analysing resilience architectures.

35. Conclusion

Competition law and resilience architectures are increasingly interconnected. Traditional competition law protects rivalry, but modern digital and infrastructure markets require attention to the structural conditions that allow rivalry to survive shocks and technological change.

The principal competition-law objectives are:

  1. preventing single-point competitive failures;
  2. preserving alternative suppliers and platforms;
  3. maintaining interoperability;
  4. reducing artificial switching barriers;
  5. preventing exclusionary vertical integration;
  6. protecting potential and dynamic competition;
  7. preventing control over essential gateways from becoming foreclosure power;
  8. preserving competitive access to important data and infrastructure;
  9. using merger control to prevent unnecessary elimination of independent competitive nodes; and
  10. designing proportionate remedies that preserve both competition and investment incentives.

The case law demonstrates that resilience is best understood not as a separate competition-law offence, but as a structural objective supported through established doctrines of abuse of dominance, essential facilities, vertical foreclosure, merger control, interoperability, exclusionary conduct and digital-market regulation.

Core cases to remember

  1. United States v. Microsoft Corp., 253 F.3d 34 (D.C. Cir. 2001) — technological foreclosure and interoperability.
  2. Microsoft Corp. v. Commission, T-201/04 — interoperability and viable competition. 
  3. Bronner v. Mediaprint, C-7/97 — limits of compulsory access.
  4. Slovak Telekom v. Commission, C-165/19 P — infrastructure access and margin squeeze. 
  5. Intel Corp. v. Commission, C-413/14 P — exclusionary rebates and competitive foreclosure. 
  6. Google Android, T-604/18; C-738/22 P — ecosystem foreclosure and platform architecture. 
  7. Google Shopping, AT.39740 — gateway control and self-preferencing. 
  8. Meta/Giphy — acquisition of a potential competitor and access to an important ecosystem input. 
  9. Broadcom/VMware, M.10806 — interoperability as a merger remedy. 
  10. Amazon Marketplace, AT.40462/AT.40703 — data, platform neutrality and access conditions. 

Exam proposition: Competition law contributes to resilience not by requiring redundancy for its own sake, but by preserving the contestability, interoperability, independent access and alternative competitive pathways that prevent a market from becoming dependent upon a single undertaking or technological architecture.

 

 

LEAVE A COMMENT