Platforms and Data Formats Supported
The modular design of the Wombat feed handler architecture makes it
relatively straightforward to support multiple platforms, formats and
protocols from within a single consistent architecture. This flexibility
is achieved by using Wombat’s Platform Agnostic Publishing API (PAPA)
abstraction layer. PAPA provides a clean abstraction between the modules that manage
exchange connectivity, data parsing and the components that publish to the
middleware. Among many other benefits, PAPA makes it possible for us to
enable all of our feed handler products to support new market data
platforms by porting a single API. Other features of PAPA that make feed
handler development easier include data caching, fault tolerance,
centralized administration, and entitlements support. A more detailed discussion of the Wombat PAPA API is included in the
online white paper downloadable from the website. Market Data Platforms Supported
| Format | Comments | Status |
|---|
| Market Feed | RMDS & Triarch | 2000 | | Qforms | ciServer/SASS | 2000 | | TIB Classic | Original Platform | 1999 | | TIBCO Rendezvous | MDRV | 2002 | | MAMA/RV | MAMA platform with TIB/RV as transport (compatible with
MDRV) | 2004 | | MAMA/Elvin | MAMA platform with Mantara Elvin as transport | 2004 | | MAMA/Wombat | MAMA platform with high performance Wombat
transport | 2004 | | kdb | Kx Systems TCP/IP | 2002 | | QAI | QAI Fast-tick interface | 2002 | | TIBCO SmartSockets | Proof of concept version developed | Beta (2003) |
Proprietary Formats or Data Buses
Due to the flexibility of the PAPA framework, Wombat feed handlers
have been ported to support a number of customer proprietary message
buses. To date, these projects have been approached in one of two
ways: Wombat develops a custom PAPA publisher based on a customer
spec. Wombat provides the customer with a sample publisher “shared
object” which may be loaded into the (PAPA based) feed handlers. The
customer then implements his or her own publishing interface that
can be loaded into a feed handler framework.
In both cases, most of the general engineering functions of the
feed handlers (subscription management, fault tolerance, etc) are
available with the custom feed handler. Generally the integration takes
4-8 weeks for development and testing, though the time does vary
significantly depending on the platform. Once the basic integration has been completed any feed handler (or
internal publisher) from the Wombat feed handler suite will be supported
on the proprietary platform.
|