Carlos AlvaradoTechnology Solutions Architect
Contact

Multicloud interconnection

Rationalizing organically grown cloud consumption into an interconnected architecture.

My role
Interconnection architect
Context
Retail enterprise
Project status
Architecture design

Design scope

  • 5named cloud platforms
  • Dynamicconvergence in the design

Five named cloud platforms. Dynamic convergence is part of the design; no measured convergence time was supplied.

Conceptual illustration · not a client topology

Inside the work

Design approach

  1. Map consumption

    Separate user-facing services from replication flows and their different bandwidth and latency needs.

  2. Interconnect

    Use Equinix for carrier-neutral connectivity across cloud platforms.

  3. Reuse & constrain

    Reuse the existing SD-WAN fabric with Cloud OnRamp; reserve Layer 2 extension for genuine requirements.

  4. Engineer traffic

    Design dynamic convergence and consumption shifts using telemetry rather than manual intervention.

Decisions & trade-offs

Architectural reasoning based on the supplied project account.

Reuse the WAN investmentSD-WAN Cloud OnRamp

SD-WAN Cloud OnRamp

Cloud connectivity leveraged the client's existing SD-WAN fabric instead of building a parallel path.

The trade-off

The cloud path must be designed in the context of the existing WAN's policy and operating model.

Limit Layer 2 extensionOTV where genuinely required

OTV where genuinely required

Data center interconnect used OTV for workloads requiring Layer 2 extension, primarily replication.

The trade-off

Extending a broadcast domain carries dependencies; it should follow the workload requirement.

Distinguish traffic needsService traffic and replication

Service traffic and replication

Replication traffic has different bandwidth and latency characteristics from user-facing flows.

The trade-off

One uniform forwarding policy would obscure those different requirements.

Technologies by purpose

Cloud platforms

  • Azure
  • AWS
  • Google Cloud
  • IBM Cloud
  • Oracle Cloud

Interconnection & traffic engineering

  • Cisco
  • Equinix
  • SD-WAN Cloud OnRamp
  • OTV

Scope & evidence

About this case

Project description supplied from LinkedIn. The visual model is a simplified reconstruction, not the client's original diagram.

Carlos on LinkedIn

Project account

An interconnection architecture with requirement-specific connectivity and telemetry-informed traffic engineering. No measured convergence or bandwidth result was supplied.

Owner-reported account. Private client configurations and original architecture documents are not published with this case.