Use Cases
This section describes the connectivity patterns the platform supports, from single-session counterparty links to multi-environment promotion workflows. Each pattern has a dedicated page that explains the intent, the conceptual flow, and what the platform guarantees.
Pick the pattern closest to your situation and follow the link. If more than one applies, compose them: a multi-venue deployment typically combines Venue Connectivity (for each session) with Multi-Venue Aggregation (for the normalized output) and Multi-Environment Promotion (to move configurations between environments).
Pattern routing matrix
| I need to... | Pattern | Adapters |
|---|---|---|
| Connect to a single counterparty over a persistent session. | Venue Connectivity | 1 |
| Accept an inbound connection from a counterparty. | Venue Connectivity (Acceptor) | 1 |
| Translate between two protocols or formats through a broker. | Protocol Bridging | 2 |
| Split one feed across multiple destinations by content. | Fan-Out and Drop Copy | 1 |
| Duplicate a feed to several destinations such as risk, surveillance, or compliance systems. | Fan-Out and Drop Copy | 1 |
| Aggregate feeds from many counterparties into one normalized output. | Multi-Venue Aggregation | 1 per venue |
| Promote configurations across dev, staging, and production. | Multi-Environment Promotion | N/A (ops workflow) |
| Connect to a system whose protocol is not built in. | Custom Protocol Integration | 1 + custom plugin |
How the patterns relate
| If you start with... | You often grow into... |
|---|---|
| Venue Connectivity | Multi-Venue Aggregation, Fan-Out and Drop Copy |
| Protocol Bridging | Fan-Out and Drop Copy |
| Multi-Venue Aggregation | Custom Protocol Integration |
See also
- For protocol-specific connector reference, see the Official Plugins section.
- For the end-to-end deployment workflow, see the Production Deployment Runbook.