HTTP/3
The latest version of the HTTP protocol that replaces TCP with QUIC as the transport layer. HTTP/3 eliminates TCP head-of-line blocking, reduces connection establishment latency, and provides built-in encryption for improved performance on unreliable networks.
HTTP/3 solves a remaining performance issue from HTTP/2: because HTTP/2 multiplexes streams over a single TCP connection, a lost packet blocks all streams until retransmission completes. QUIC, the transport protocol underlying HTTP/3, multiplexes at the transport layer so packet loss on one stream does not affect others. Additionally, QUIC combines the TLS handshake with the transport handshake, establishing secure connections in a single round trip.
For AI products serving global users, HTTP/3 provides meaningful performance improvements, especially on mobile networks where packet loss is common. AI features that make multiple API calls benefit from QUIC's independent stream handling because a slow response from one AI endpoint does not delay others. Growth teams targeting mobile users or users in regions with unreliable networks will see measurable improvements in page load times and AI feature responsiveness. Adoption is growing rapidly with support from major CDNs, browsers, and cloud providers, making HTTP/3 an increasingly standard infrastructure component for performance-conscious AI products.
Related Terms
Content Delivery Network
A geographically distributed network of proxy servers that caches and delivers content from locations closest to end users. CDNs reduce latency, improve load times, and absorb traffic spikes by serving content from edge nodes rather than a single origin server.
Edge Computing
A distributed computing paradigm that processes data closer to the source of generation rather than in a centralized data center. Edge computing reduces latency, conserves bandwidth, and enables real-time processing for latency-sensitive applications.
Serverless Computing
A cloud execution model where the provider dynamically manages server allocation and scaling. Developers deploy functions or containers without provisioning infrastructure, paying only for actual compute time consumed rather than reserved capacity.
Function as a Service
A serverless computing category where developers deploy individual functions that execute in response to events. FaaS platforms like AWS Lambda, Google Cloud Functions, and Azure Functions handle all infrastructure management, scaling each function independently.
Platform as a Service
A cloud computing model that provides a complete development and deployment environment without managing underlying infrastructure. PaaS offerings like Heroku, Vercel, and Google App Engine handle servers, storage, networking, and runtime configuration.
Infrastructure as a Service
A cloud computing model that provides virtualized computing resources over the internet. IaaS offerings like AWS EC2, Google Compute Engine, and Azure Virtual Machines give teams full control over servers, storage, and networking without owning physical hardware.