Mar 18, 2026 · 1 min read · Architecture

Network Fabrics for Private Cloud

Underlay design, EVPN/VXLAN thinking, MTU discipline, and failure-domain engineering for private cloud network fabrics.

Last reviewed: 2026-03-18

Fabric Design Goals

Private cloud fabrics should provide deterministic forwarding, predictable convergence, and enough visibility to explain east-west traffic behavior during maintenance, failure, and rebuild events.

Key Principles

  • Keep underlay design boring and consistent.
  • Treat MTU consistency as a non-negotiable prerequisite.
  • Separate control, storage, and tenant traffic with explicit QoS thinking.
  • Validate route convergence and ECMP behavior under realistic fault scenarios.

Validation Checklist

  1. Pull a top-of-rack device from service during real application traffic.
  2. Measure the impact of storage rebuild traffic on tenant flows.
  3. Validate packet size behavior with overlays enabled and appliance paths included.
  4. Confirm observability at both host and fabric layers.

Why This Matters for Platform Choice

Integrated platforms can reduce day-2 friction if their network abstractions line up with the fabric design. More modular platforms can be equally strong, but only when teams own the network model end to end.