SRSE
The SpiderRock Storage Engine (SRSE, pronounced "SAR-see") is our proprietary relational database that provides an SQL interface to the SpiderRock Connect Live Messaging Platform. SRSE consists of a MariaDB 10.11.4 database whose data is managed by our proprietary in-memory storage engine.
- Live Data Access: SRSE listens to all live records on the SpiderRock message bus and makes the current leading-edge data available via standard MySQL bulk
SELECTsyntax. Available data includes equity, options, and futures NBBO prices, implied volatilities, Greeks, prints, risk records, and more. - Order and Data Upload: SRSE is a high-throughput gateway via which clients can easily upload parent orders that are tightly integrated with SpiderRock Connect's execution algorithms and GUI tools. Clients can also upload position files, locates, restricted lists, and theoretical models. Rows inserted into SRSE tables are published as live data records that are then consumed elsewhere in the platform.
Note:
Many of the live multicast streams that feed data to SRSE servers can be accessed directly from the wire using SpiderRock Connect's multicast packet handling libraries or by integrating our packet layouts directly into your multicast gateway(s). Contact the Client Support Desk for more details.
SRSE Databases Summary
SRSE consists of the following nine databases:
| SRSE Database | Description | Learn More |
|---|---|---|
| SR Analytics | - Live and prior day SpiderRock Connect live surfaces - Live and prior day implied volatilities and greeks - Rate curve, dividend, and earning estimates - Historical underlying volatility tables | Query Guide Message Schemas |
| SR Trade | - SpiderRock Connect equity, option, and future parent order management - Parent order executions and parent order reports - Multi-leg parent order management - Upload away executions (drops) | Query Guide Message Schemas |
| SR Live | - U.S. equity, option, and future live quotes and prints - Product definition tables (OCC, CME, ICE, & Equity NMS) - Complex order book quotes and exchange imbalances - High throughput bulk access to full market data universe | Query Guide Message Schemas |
| SR Spread | - U.S. equity options live quotes - U.S. options on futures live quotes and prints - Futures spread market tables | Query Guide Message Schemas |
| SR Auction | - Normalized equity option single leg and complex auction feeds - Auction result analytics | Query Guide Message Schemas |
| SR Risk | - Prior day SpiderRock Connect archived positions and marks - Start-of-period clearing firm positions and marks - SpiderRock Connect executions and inbound away drops - Live position greeks and slide risk across entire portfolio | Query Guide Message Schemas |
| SR Control | - View and manage symbol and user supervisory trade risk controls - Manage borrow rates, locates, and restricted trading lists - Dynamically control algo configuration and delivery instructions - Integrated with SpiderRock GUI tools | Query Guide Message Schemas |
| SR Theo | - Upload parameterized or splined theoretical volatility surfaces - Download per-strike theoretical volatilities, price, and greeks - Manage buy/sell/volatility levels for idea generation and position evaluation - Integrated with SpiderRock GUIs and other SRSE tables | Query Guide Message Schemas |
| SR Flex | - Live FLEX Option Prints - Pricing of multi-leg FLEX option strategies - Support for variable-strike legs to target a desired spread premium | Query Guide Message Schemas |
How to Connect to SRSE
All SRSE servers are located in the SpiderRock Connect datacenters and managed by SpiderRock. Access to SRSE is available via a MariaDB TCP connection using an assigned address/port combination. For the exact IP address and port number, please review the SRSE Servers page.
SRSE servers are available in our NY5 (Secaucus, New Jersey) datacenter and can be accessed via cross-connect or any suitable network connection, including VPNs over the public internet. SRSE can be accessed using SQL console tools or database drivers capable of connecting to MariaDb 10.11.4 or later.
DocTables and DocColumns
Each SRSE database contains two tables that have metadata about the tables in that database:
- The
docTablestable contains descriptions for the tables available within that SRSE database. - The
docColumnstable contains column descriptions, default values, repeating group schemas, and additional column metadata.
- DocTables
- DocColumns
SELECT * FROM SRLive.`docTables`;
SELECT * FROM SRTrade.doccolumns WHERE table_name ='msgoptordergateway'
ORDER BY ordinal_position ASC;
Workflow Example: Implementation of a Systematic Strategy
A typical approach to implement a systematic trading strategy via SRSE can be summarized with the following steps using the coding language of the client’s choice:
- Select the target strike greeks from the msgOptionImpliedQuote table (SRAnalytics).
- Select current risk tallies for all associated executions so far today (SRRisk).
- Compose a parent order basket based on the results from the above queries as well as any additional risk or order handling parameters and insert back into the msgOptOrderGateway table, usually using “LOAD DATA INFILE” syntax. (SRTrade)
- Monitor working parent orders by repeatedly selecting from the msgSrOptBrkrState table (SRTrade) and/or watching the Order Manager tool.
- Monitor any resulting fills by either repeatedly selecting from the msgSrParentExecution table (SRTrade) and/or watching the Order Manager tool.
- Clients typically iterate through the same process to achieve objectives.
Note:
If necessary, SpiderRock Connect can drop orders and fills back to the client via FIX, even if the orders were originally uploaded via SRSE.