Limitations and performance of HTTP Sequencer Connections

Canton supports both HTTP and gRPC sequencer connections. However, I couldn’t find any documentation on the potential downsides of using an HTTP connection here while in some settings it can be easier to deploy.

Looking through the code I did find out that HTTP connections don’t seem to support specifying multiple URLS for fallbacks. Are there any other restrictions? How does performance compare between the two?

The supported sequencer implementations do not currently expose HTTP APIs, but only gRPC APIs.
The class HTTPSequencerConnection is there only for certain testing and development purposes where gRPC is not an option.

1 Like