The MarketFactory-provided software which MarketFactory customers link into their local application in order to connect to the MarketFactory Whisperer APIServer.

The MarketFactory API (MFAPI) Client consists of little more than a message encoding and decoding layer that presents the contents of messages to callback functions.

MarketFactory has specifically limited the work performed within the MFAPI in order to minimize Client-side latency and maximize stability.

Handler

The Customer-written software which performs different actions on reception of messages of various types from the APIServer. This inherits from the MFHandler class.

Message

A MFAPI message is an application-level protocol data unit which is received by an MFClient object, and is passed to the appropriate function in a user-supplied class derived from MFHandler,  based on its type. 

Market

The MarketFactory name for a given instrument, for example EUR/USD for spot FX, or 6EH6 for CME Eurodollar futures expiring in March 2016. 

Whisperer

The generic name for the MarketFactory server software. A Whisperer installation consists of an APIServer (which faces the customer), and one or more FeedServer components (which face the exchanges), as well as auxiliary data-logging components which are used internally and do not interact directly with the outside world.

The API Server 

The API Server acts as the interface to which the customer infrastructure connects. It creates the customer sessions to the Whisperer platform and permits the customer infrastructure (and the associated users) to gain access to the Venue connections configured for the instance. As the only interface for the customer infrastructure (using the classic implementation), the API Server is also the site of the session handling processes associated with customer connections to Whisperer prior to feed/venue connection subscription.

DB Logger

The DB Logger applies the user authentication requirements for Whisperer, through use of a database. Ensuring that only users established within the designated customer infrastructure, listed individuals, known devices etc.. are the only users granted access to the platform and associated connections. failure to authenticate with the DB Logger will result in the customer infrastructure or user(s) being rejected. These user entries can be made directly to the database or explicitly to a static configuration.

DC Server

The Drop Copy Server (or DC Server) generates a stream of MFAPI TradeCapture Messages. MarketFactory can thenallowanMFAPIClient to subscribe to these messages, similar to a traditional FIX drop copy using the MarketFactory protocol instead. This is an additional feature that can be enabled for customers, the benefits of which are described in more details below (under additional services).

Feed Handlers

Every Trading Venue that MarketFactory's Whisperer is able to integrate with has a FeedServer (a term used synonymously with Feed Handler) which makes the integration possible. The Feed Servers connect directly with the API server via the Classic MFAPI.

Customer infrastructure can connect directly to the Feed Server (for market data only) using MarketFactory's SBE3 implementation, avoiding the risk of bottlenecks in the API server (which traditionally has been the only interface available to the customer infrastructure). This approach is not only aimed at reducing latency at times of high message frequency but also improves high availability by reducing dependency on access to the API server in order to obtain market data from Trading Venues.

The Feed Servers also exist as a source of normalisation, by integrating venue messages, tags and fields to align with the MarketFactory message protocol resulting in a Feedserver that aims to be as closely compatible to the venue as possible, whilst maintaining a normalised library of messages to smooth out the differences between differing trading venues and their protocols.

Additional Services

The Whisperer platform is also supplemented with additional features provided by MarketFactory, that enhance the benefits available to customers outside of connectivity alone. These optional modules are explained in detail in further chapters.

TBD Example.

Eg Flow asked: 

Use multiple logins > same MF gateway IP + Port using the same venueID.

. Refer to Additional Services for further detail.