Skip to content
Networking·Intermediate·Conceptual·1 min read

Why is domain sharding an anti-pattern under HTTP/2?

Short interview answer

Sharding split assets across subdomains to get past the six-connection-per-origin limit. Under HTTP/2 that limit is gone, and each extra domain now costs a fresh DNS lookup, TCP handshake, and TLS negotiation, and fragments the single connection's multiplexing and prioritization.

Key takeaway

Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.

← Back to HTTP/2, HTTP/3, and connection performance

Related questions