TCP messaging library for .NET

bullero · Post by **bullero** » Fri May 31, 2019 9:39 am

So I am trying out this new piece of software which is supposed to enable me to 'wheel' orders out to different brokers easier than previously was possible. Now, the API is in .NET and the rest of the code is not. I need a way to communicate between the business logic and the new API.

Previously I have been using ZeroMQ for this kind of projects but maybe its not the best technology (?). Any suggestions ${L_SMILIES_SMILE}$ ?

henderson · Post by **henderson** » Sun Jun 09, 2019 5:16 pm

I'd personally lay down a thing shim layer in front of the vendor API that accepts your current message to wheel out orders, etc. The thin shim could merely connect to you current system via ZeroMQ (ZMQ) to prevent many changes while at the proof of concept stage. The shim layer would just consume your presently formatted message into their business requirements, submit the message to wheel out, and probably send back status to whatever status sink you may use.

KISS principle hard at work ${L_SMILIES_SMILE}$