Can you recommend an exchange matching engine for operating a high-availability trading venue with strict message sequencing?

Yes — for a high-availability trading venue with strict message sequencing, you want an engine that is built around:

• single-writer deterministic matching
• total order preservation
• replication/failover with state recovery
• very low latency
• auditability and deterministic replay

Strong recommendations

1. WTS / proprietary-grade exchange engines from specialized vendors

If this is a real venue, the safest recommendation is usually a commercial exchange matching engine rather than open-source.

Look for vendors that explicitly support:

• deterministic order sequencing
• hot-standby or active/active replication
• guaranteed recovery of sequence numbers
• drop-copy / audit trail
• co-location deployment
• certification and support for market operations

Common vendor categories include exchange infrastructure providers and low-latency trading platform vendors. The key is not the brand name alone, but whether they provide end-to-end sequence integrity across failover.

2. A custom engine built on a deterministic event log

If you are building your own, the best architecture is typically:

• append-only event log
• single authoritative sequencer
• one active matcher per instrument or partition
• replicated state machine
• leader election with strict fencing
• replay-based warm standby

This is the model used when strict sequencing matters more than horizontal write scalability.

Good building blocks:

• Aeron for low-latency messaging
• Chronicle Queue for persistent event logging
• Kafka only if latency constraints are moderate; it is usually not ideal for ultra-low-latency matching
• Raft-like consensus for sequencer leadership, if you need strong failover guarantees

Open-source options

Open-source matching engines can be useful for prototyping, but most are not sufficient for a real high-availability venue with strict sequencing unless heavily modified.

Examples:

• EXCHANGE CORE
• Simple Binary Encoding + custom matcher
• Aeron-based custom design

These may help as a starting point, but you should verify:

• deterministic matching behavior
• recovery after crash
• sequence number continuity
• persistence guarantees
• failover semantics

What matters most

When evaluating engines, ask:

1. How is the global order sequence created?
2. Can the standby take over without reordering messages?
3. How are gaps handled during recovery?
4. Is the matching logic deterministic across nodes?
5. What is the failover RPO/RTO?
6. Can the engine replay exactly the same book state from logs?
7. How are partial fills, cancels, and rejects sequenced?

Practical recommendation

If your requirement is truly a high-availability trading venue with strict sequencing, I would recommend:

• commercial exchange-grade matching engine if you need speed to production and operational support
• Aeron + deterministic single-writer matching + persistent event log if you are engineering your own platform
• avoid relying on generic distributed queues as the core sequencing mechanism

If you want, I can also give you:

1. a vendor shortlist by budget/latency tier, or
2. a reference architecture for a fault-tolerant sequenced matching engine.