Processes

Converts a .json file to a transaction log file.

Reads messages from one or more Kafka topics, converts them into MarketGrid transactions, and publishes the replies onto another topic.

Publishes market data objects onto a Kafka topic.

Converts a file from MG transaction log format to one or more .tsv files.

MDB real-time alert processing engine. This process uses the data in the various tables related to alerts, such AlertDefinition, AlertCategory and AlertConfiguration to generate alerts which are sent to the matching engine as transactions and are then populated in the Alert table. Alerts can be triggered by any data in shared memory and are defined by the data in the AlertDefinition table (and others). A common example would be an alert which pops up in the trading UI when a resting order is matched. Another example could be email notifications for an auction starting etc. See the full list of tables related to alerts here.

MDB discovery service.

MDB query gateway.

MDB historical database.

MDB real-time engine that produces 24-hour rolling market data. This process calculates values such as total volume traded in the past 24hr window every second and sends LevelOneUpdate transactions to the engine. It queries the historical and realtime databases to calculate this. The transaction contains the sequence number of the most recent record included in the calculation and the engine checks if there are any more recent records and updates the value accordingly (relevant for calculations such as last 24h high/low).

MDB Migration process for database maintenance.

MDB process monitoring service.

MDB real-time database.

MDB report generation process.

The web server used to deliver the MarketGrid UI.

Empty nq process which can be used to run a compiled nq script.

Prometheus Exporter

Unlink all MarketGrid objects from shared memory.

Print the contents of a transaction log file or shared memory table.

Prints transaction timings recorded by the matching engine when the --dotransactiontiming option is used.

The MarketGrid matching engine.

Arbitrates between Main and Backup matching engines.

Prints shared memory usage.

Transaction server which accepts transactions, routes them to the matching engine, and returns the replies.

Triggers a system cycle on a configurable interval or in response to a shared memory condition.

Converts a .tsv file to one or more transaction log cache files.

UI Load Emulator

Server which services UI clients over WebSockets and REST.