Market Gateway
Market Gateway provides live market data and managed broker orders over gRPC. The services share encrypted broker credentials and reusable sessions in MongoDB.
| Service | Responsibility | Default port | Client authentication |
|---|---|---|---|
| Market Data | Arrow dataframe snapshots and best-limit streams | 8080 | x-api-key metadata |
| OMS Bridge | Accounts, broker queries, managed orders and raw broker feeds | 8080 | Bearer token |
| Session maintenance | Scheduled validation and replenishment of broker sessions | None | Internal process |
| Update job | Catalogue, holidays, account information and subscription recovery | None | Internal command |
Start here
Section titled “Start here”- Run the services and configure their shared database.
- Consume market data and understand its dataframe schemas.
- Connect a Bridge client and use managed orders.
- Operate the deployment and understand sessions and recovery.
- Browse the generated API reference or download its protobuf contracts.
Service boundaries
Section titled “Service boundaries”The supplier opens broker feeds directly using the shared OMS adapters. It does not call Bridge gRPC. Each process acquires reusable sessions on demand; maintenance is an aid to availability rather than a prerequisite for acquisition.
Order recovery and trading workers belong to the Bridge process. Market Data, maintenance and the update command do not access the order journals. Run one Bridge and one supplier per database.
The standalone supplier does not migrate Noname consumers or historical data. Handle metadata/history access and data transfer separately before redirecting them.