May 6, 2010 at 12:35 am
Hey All.
Please have look at the following scenario and help me decide which direction would serve the best solution to this problem.
An in-house trading system (Portfolio Manager) will allow traders to place orders for stock that need to be bought on the local and international stock exchanges. These orders are placed in a SQL server database.
Then we have a server with all the 3rd Party Trading API licenses. This server will run an automated system (Execution Manager) that will collect these orders, consolidate them and send them off through the correct 3rd Party API.
We basically want Execution Manager to be notified when a new batch of orders has been placed in SQL Server from Portfolio Manager, without Execution Manager having to look in the database every 60seconds. Execution Manager should only have to an “Ear-To-The-Ground” for a signal from SQL.
Which approach will best suite this problem.
My findings so far:
1. Service Broker
Setting up a decent Service Broker.
2. Time Interval Data Search
The Execution Manager will check for new orders every 60seconds
3. Table Triggers
When data enters the order table and alert of some sort will be send to the Execution Manager.
[font="Courier New"]-----------------------------------------------------------------------------------------------------------------------
😀 Arguing with Programmers are like wrestling a pig in mud, soon you realize the pig is enjoying it. 😀
-----------------------------------------------------------------------------------------------------------------------[/font]
May 6, 2010 at 5:13 am
I would suggest to go about Trigger optioto send alert or database mail whne order is come to database. This is good to maintane as we have good control over it.
Service broker is also good option wwhich do similar functionality as above with more features. But maintaning service broker is bit problamatic in such a scenerio.
Now it's your call 🙂
May 7, 2010 at 12:32 am
I have considered the triggers at a certain point.
But the Portfolio Manager will not just send one order and expect the Execution Manager to pick it up. It can send 1000s of order in a matter of minutes. Once the complete batch has been transferred to to the database. It then needs to let the execution system know that it can go-ahead and process the orders.
Otherwise the Execution system is alerted of an order when the first trigger fires. And will probably miss a lot of orders if it starts processing immediately.
[font="Courier New"]-----------------------------------------------------------------------------------------------------------------------
😀 Arguing with Programmers are like wrestling a pig in mud, soon you realize the pig is enjoying it. 😀
-----------------------------------------------------------------------------------------------------------------------[/font]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply