In optical networking, DCI refers to Data Center Interconnect. Network links that connect separate data centers for traffic exchange, replication, backup, and workload mobility. Engineers commonly encounter it while planning or operating Metro and regional data center connectivity.
For DCI, interoperability and acceptance start with the governing specification. The design context may include Ethernet, RoCEv2, InfiniBand, congestion control, and the scale-up or scale-out topology used by the compute system. Project documentation should identify the edition, host assumptions, and any vendor-specific limits that apply.
DCI should not be treated as another name for Leaf-Spine Network. DCI is defined here as Network links that connect separate data centers for traffic exchange, replication, backup, and workload mobility. By comparison, Leaf-Spine Network means a two-tier data center topology in which every leaf switch connects to every spine switch for predictable low-latency east-west traffic. The two concepts may appear in the same design, but they answer different engineering or purchasing questions.
For a deployable DCI requirement, record topology, oversubscription, traffic pattern, congestion control, latency target, failure domain, and scale. Do not infer those details from RDMA or from a headline speed alone, because the related concept is defined separately as Technology allowing one computer to access another computer's memory directly with minimal CPU involvement.
Frequently Asked Questions
Are DCI and Leaf-Spine Network interchangeable?
No. DCI describes Network links that connect separate data centers for traffic exchange, replication, backup, and workload mobility, while Leaf-Spine Network describes a two-tier data center topology in which every leaf switch connects to every spine switch for predictable low-latency east-west traffic. Confirm both separately when the design uses both concepts.
Where is DCI normally used?
Typical use includes Metro and regional data center connectivity. The exact implementation still depends on the host equipment, link design, environment, and governing specification.
What should a DCI specification include?
It should state topology, oversubscription, traffic pattern, congestion control, latency target, failure domain, and scale. These details allow a supplier or engineer to verify the requirement instead of relying only on the term DCI.
Need help selecting a compatible transceiver?
Tell us your target platform, data rate, fiber type, and transmission distance.