Liquid cooling is not one product. It is a chain of interfaces from the silicon package to the outdoor heat-rejection equipment. The correct architecture depends on heat flux, rack density, facility temperatures, service model, water constraints, and deployment speed.
Start with the heat path
Define which components move to liquid, what remains on air, and where each thermal boundary sits. A direct-to-chip system commonly includes cold plates, server hoses, quick disconnects, rack manifolds, a technology cooling loop, a CDU, and a facility loop. Immersion changes the hardware and service boundary by placing most or all IT components inside a dielectric bath.
- Processor and rack design heat loads
- Liquid capture ratio and residual air load
- Technology-loop supply and return temperatures
- Facility approach temperature and design-day heat rejection
Normalize supplier ratings
A megawatt label is not enough. Capacity changes with coolant temperatures, flow, pressure, fluid properties, redundancy state, and the allowed approach across heat exchangers. Compare vendors at one project duty point.
- Net capacity with one redundant component unavailable
- Pumping power and pressure drop at the selected duty
- Water quality and wetted-material requirements
- Controls, alarms, telemetry, and fail-safe behavior
Design the operating model with the equipment
Liquid systems change commissioning, leak response, maintenance, spare parts, fluid testing, and server service. Include operations teams before freezing the mechanical design.