Questions About Connector Design

[zzho325]

Thanks for the great work! I’m interested in contributing to connector and adding a Coinbase implementation and wanted to clarify a couple of design points

• Multiple live bots
  Does the connector support multiple live bots connecting simultaneously? I’ve noticed that in this case currently when one bot subscribes to an instrument, every bot connected to that same connector also receives the feed. Is that the intended behavior, or would it make sense for the connector to publish only to the bot that requested it?

• Cleaning up subscriptions
  It looks like when a bot exits, its subscription on the connector stays alive. Would it make sense for the connector to automatically clean up subscriptions for bots that are no longer active?

Thanks so much!

[nkaz001]

Currently I’m considering migrating the current Iceoryx-based IPC to TCP, as TCP offers greater reliability and compatibility. Additionally, a truly low-latency implementation ultimately requires careful fine-tuning and optimization based on the specific strategy, exchange, and other factors. Since this framework is designed for general use, it’s more practical to treat it as a quick prototyping and testing.

• Multiple live bots
  Does the connector support multiple live bots connecting simultaneously? I’ve noticed that in this case currently when one bot subscribes to an instrument, every bot connected to that same connector also receives the feed. Is that the intended behavior, or would it make sense for the connector to publish only to the bot that requested it?

The current design has some flaws and limitations. The design aims to minimize data copies when publishing market data for the same symbol. But, based on my understanding, Iceoryx’s current implementation has a constraint: if you create multiple pub-subs and read from them, you must read sequentially from each one. To simplify this and reduce the overhead of sequential reads, I opted for a single request pub-sub and a single publish pub-sub. But, as you pointed out, this design forces every bot connected to the same connector to receive market data for all subscribed symbols.

• Cleaning up subscriptions
  It looks like when a bot exits, its subscription on the connector stays alive. Would it make sense for the connector to automatically clean up subscriptions for bots that are no longer active?

Iceoryx doesn’t offer any built-in connection control. We need to implement custom logic to track whether any bots have alive connection to check if the symbol subscription is needed. So currently, there’s no cleanup mechanism for symbol subscriptions.

I may prioritize transition to TCP, I'm unsure if I will additionally implement Iceoryx-related features.

[zzho325]

Hi @nkaz001, thanks for the detailed clarification!