Platform Architecture

RAP - The Trading Edition platform architecture includes feed handlers, publishers, and subscribers.

RAP writes in-bound market data to an in-memory cache database and a historical data store. The cache database is an Adaptive Server® Enterprise (ASE) database; the historical data store is a Sybase® IQ database.

Unified Agent Framework (UAF) provides a common set of discovery services, and host agent plug-ins that manage server resources or perform various operations. Agent plug-ins can perform product-specific commands, including status, start, stop, and restart. The agent can also help retrieve the log file of the server.

• Feed Handlers
  Feed handlers direct inbound market data into the RAP environment. They are publishers that manage connectivity and message transformation directly from exchanges, like the NYSE, or consolidated service providers, like Reuters.
• Publishers
  Publishers format incoming market data messages, and forward those messages to a subscriber.
• Subscribers
  Each subscriber has two components: the open subscriber and a data stream handler. The open subscriber handles interface issues and queues messages for the data stream handler, and the data stream handler routes the messages to their final destination.
• RAPCache Database
  The RAPCache database is an Adaptive Server® Enterprise database server, which provides near real-time access to inbound market data messages.
• RAPStore Database
  The RAPStore database is a Sybase IQ disk-based repository that can store large (into the petabyte range) amounts of historical data.
• Operations Console
  Operations Console is a Web-based console that monitors system status and performs routine administration tasks.
• Process Flow
  Message processing occurs in three phases: build, transfer, and load.
• Transfer and Truncation of Derived Data
  RAP infrastructure supports high-speed transfer of derived data into the RAPStore, with minimal latency.