Implementation of Multi-Channel Message Queues using QUIC

In modern architecture, message queues are a critical component. They help us establish a buffer to cope with different speeds of data being produced and consumed. While message queues like RabbitMQ have matured and have become a go-to name for message queues, it uses TCP as the transmission control layer and thus suffers from the limitations of TCP. RabbitMQ has implemented a feature called channels, where multiple channels can be created on the same TCP connections. These channels are implemented on the application layer. An improvement to this implementation which replaces TCP with QUIC as the transmission protocol is proposed, because of which multiple channels can correspond to individual streams on the same QUIC Connection. This will eliminate the Head-of-Line blocking problem. In the scope of this research paper, we experiment with this implementation and focus on only this feature, while improvement to the message queue by use of QUIC is not limited to just this. Our experiments show an 88% increment in latency in RabbitMQ when comparing a single-channel connection with 5-channel connections, while with QUIC the increment is only 1.63%.