Imported from previous forum
Our Fix engine provider has multiple interface support into their FIX engine.
I am to use either their TIB or In-process interface for our client-to-fixEngine connection.
Our client product is actually a java server that translates standard FIX messages from/to fix vendor to our internal message structure.
OurAppServer <–> OurClientProduct <–> FixVendor
^ ^
| |
| |
our standard
message fix
format messages
so for In-process interface, OurClientProduct will be running in process with the FixVendor product.
with TIB interface, it would communicate using TIBCO Randevouz with the FixVendor out of process.
I just need some feedback as to what would be the benefits of one over another(using TIB vs. using In-process).
specifically architectual benefits of using one for the other.
-would load balancing or high availability be easier using one or the other.
-would it be faster to use Inproces or TIB
-which one have your folks worked on that you like, etc.
We use TIB for our distributed applications and so cost is not an issue for license since we have one already.
TIA for all your comments. My architectual knowledge in this area is very weak so I cant see beyond my nose. yet.
j.l.