Before you move to HTTP/3 ...

Summary

The video discusses HTTP/3's rapid adoption since becoming an official standard, with a focus on Mozilla's data showing its growing usage. It contrasts HTTP/1 and HTTP/2, highlighting potential CPU and memory usage increases with HTTP/3 due to additional parsing required for streams. The presenter anticipates future disadvantages of HTTP/3, as seen with HTTP/2, and notes the protocol's flexibility due to encryption, allowing for improvements without middleware interference. They express interest in long-term server resource implications and speculate on kernel-level QUIC implementation for efficiency.

Takeaways

• 🌐 HTTP/3 has been officially standardized for over a year and has seen a significant increase in adoption.
• 📈 The article from AP nick.net discusses the rise in HTTP/3 usage, supported by data from Mozilla showing its growth since January 2021.
• 📊 The usage of HTTP/3 has been climbing, while HTTP/1 gradually decreases, indicating a shift in technology preference.
• 🔍 The discussion highlights the lack of focus on potential disadvantages of HTTP/3, which is common in the early stages of technology adoption.
• 🤔 The speaker anticipates that, similar to HTTP/2, the disadvantages of HTTP/3 may become apparent a few years after widespread adoption.
• 🔄 There's a need for dual support of HTTP/2 and HTTP/3 as not all clients are capable of utilizing HTTP/3, necessitating compatibility.
• 💡 The script points out the importance of understanding the backend implications, such as CPU and memory usage, when transitioning protocols.
• 🛠️ HTTP/2 introduced additional computational overhead due to the need for stream parsing and protocol handling, which can increase CPU usage.
• 🔒 QUIC, the transport protocol underlying HTTP/3, operates over UDP and requires applications to handle packet ordering and connection management, potentially increasing CPU and memory load.
• 🔄 The encryption in QUIC allows for protocol improvements without the interference of middleboxes, a significant advantage over TCP.
• 🔮 The speaker speculates on future developments, including the possibility of the kernel natively implementing QUIC for more efficient handling.

Q & A

How long has HTTP/3 been an official standard?

HTTP/3 has been an official standard for over a year since the time the video script was written.

What does the article from AP Nick.net discuss about HTTP/3?

The article discusses how HTTP/3 has gained popularity and is 'eating the world', with a focus on the adoption rate and the potential advantages and disadvantages of the protocol.

What does the chart from Mozilla indicate about HTTP/3 adoption?

The chart from Mozilla indicates that HTTP/3 adoption has been increasing since January 2021, showing a rise in usage as both clients and servers started to enable HTTP/3.

Why is HTTP/1 gradually decreasing in usage?

HTTP/1 is gradually decreasing in usage because people are transitioning to HTTP/3, which is seen as an improvement over HTTP/1.

What potential disadvantages of HTTP/3 are mentioned in the script?

The script mentions that while HTTP/3 has many advantages, it also has potential disadvantages, such as increased CPU and memory usage due to the additional parsing required for streams and frames.

How does the script suggest HTTP/2 compares to HTTP/1 in terms of CPU usage?

The script suggests that HTTP/2 might have a higher CPU usage compared to HTTP/1 due to the additional work required for parsing streams and frames.

What is the significance of QUIC as mentioned in the script?

QUIC is significant because it allows for the protocol to be upgraded and improved without the limitations faced by TCP, as everything is encrypted and middleboxes do not interfere with the protocol's functionality.

Why does the script suggest that HTTP/3 might have higher CPU usage compared to HTTP/2?

The script suggests that HTTP/3 might have higher CPU usage because QUIC, which HTTP/3 is built on, requires more work in user space for tasks that TCP handles in the kernel, such as packet reordering.

What is the script's perspective on the future of QUIC and HTTP/3?

The script anticipates that over time, as HTTP/3 becomes more widely adopted, potential issues and side effects will become apparent, similar to what happened with HTTP/2. It also speculates that in the future, the kernel might natively implement QUIC, leading to more efficient handling.

What does the script imply about the current state of HTTP/2 adoption?

The script implies that HTTP/2 is currently being phased out in favor of HTTP/3, as almost everyone who had HTTP/2 has switched to HTTP/3, although HTTP/2 is still supported.

Why is it important to consider both the advantages and disadvantages of new technologies like HTTP/3?

It is important to consider both the advantages and disadvantages of new technologies to have a balanced view of their impact and to anticipate potential issues that may arise as they become more widely adopted.