TradersPost Webhook Concurrency: How Trades Are Executed
TradersPost executes trades concurrently across multiple brokers, ensuring near-instant execution. Separate webhooks for each broker are unnecessary, as all trades are processed in parallel.
Marketing
Reviewed by Mike Christensen
Fact-checked by Mike Christensen
Are Trades Executed Concurrently Across Multiple Brokers?
TradersPost is designed to execute trades concurrently across multiple brokers. If a user has a single webhook connected to four different broker subscriptions, the system will send trade execution requests to all four brokers nearly simultaneously.
TradersPost uses a message queue system to manage incoming webhook requests, but it processes these messages so quickly that execution occurs in real time. While there is a small possibility of slight variations in execution timing, all trades should be sent within milliseconds of each other.
Should You Use Separate Webhooks for Each Broker?
Some traders consider setting up separate webhooks per broker to ensure orders are processed independently. However, because TradersPost already handles concurrency efficiently, using multiple webhooks for the same strategy will not provide any execution advantage. All requests still go through the same message queue and are processed in parallel.
Key Takeaways
• A single webhook can execute trades across multiple brokers at nearly the same time.
• Trades are not processed in a serial order; execution across brokers occurs in parallel.
• Using separate webhooks for each broker will not improve execution speed.
Conclusion
TradersPost is built for concurrency, ensuring that trades are sent to multiple brokers simultaneously when using a single webhook. There is no need to create separate webhooks for each broker, as all execution requests are processed efficiently in real time.
