# Limitations and performance of HTTP Sequencer Connections

**URL:** <https://forum.canton.network/t/limitations-and-performance-of-http-sequencer-connections/6010>\
**Category:** App Development\
**Tags:** canton\
**Created:** [January 23, 2023, 10:21am UTC](https://forum.canton.network/t/limitations-and-performance-of-http-sequencer-connections/6010 "2023-01-23T10:21:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cocreature](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/cocreature/32/36_2.png) [@cocreature](https://forum.canton.network/u/cocreature)\
**Post date:** [January 23, 2023, 10:21am UTC](https://forum.canton.network/t/limitations-and-performance-of-http-sequencer-connections/6010/1 "2023-01-23T10:21:32Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![bernhard](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/bernhard/32/356_2.png) [@bernhard](https://forum.canton.network/u/bernhard)\
**Post date:** [January 24, 2023, 1:32pm UTC](https://forum.canton.network/t/limitations-and-performance-of-http-sequencer-connections/6010/2 "2023-01-24T13:32:48Z")

</div>

The supported sequencer implementations do not currently expose HTTP APIs, but only gRPC APIs.  
The class [`HTTPSequencerConnection`](https://github.com/digital-asset/canton/blob/fc624f76987f6a0893d8aa49b22bb8d1ddbc38eb/community/common/src/main/scala/com/digitalasset/canton/sequencing/SequencerConnection.scala#L62) is there only for certain testing and development purposes where gRPC is not an option.