How nickchal1/matchingengine0 works
MatchingEngine0 is a single-instrument limit order book with a TCP demo interface. The main workflow generates NewOrder messages in the client, encodes them, sends them to the server, decodes complete messages, submits them to the book, and displays trades and book state. The engine also supports cancellation and book queries through its API, though the demo server does not expose those operations. Edges reflect the sampled source and README; the documented cancellation/query capabilities are included without guessing at unsampled callers.
Main entry points: server.cpp TCP Server · OrderBook.h Order Book API · client.cpp Order Generator · Protocol.cpp Message Codec
Components 12
Networked Demo
- Order Generator
client.cpp - TCP Server
server.cpp - Scripted Book Demo
main.cpp
Binary Protocol
- Message Codec
protocol/Protocol.cpp - Wire Message Types
protocol/Protocol.h
Matching Engine
- Order Book API
engine/OrderBook.h - Validation and Matching
engine/OrderBook.cpp - Resting Book State
engine/OrderBook.cpp
Order Domain
- Order Types
engine/Order.h - Submission Result
engine/SubmissionResult.h - Trade Record
engine/Trade.h
Other components
- Demo Operator
Connections 12
- Demo Operator → Order Generator: runs demo
README.md - Order Generator → Message Codec: encodes orders
client.cpp - Message Codec → Wire Message Types: serializes fields
protocol/Protocol.cpp - Order Generator → TCP Server: sends TCP bytes
README.md - TCP Server → Message Codec: decodes messages
server.cpp - TCP Server → Order Book API: submits orders
server.cpp - Order Book API → Validation and Matching: validates and matches
engine/OrderBook.cpp - Validation and Matching → Resting Book State: updates book state
engine/OrderBook.cpp - Order Book API → Submission Result: returns results
engine/OrderBook.h - Submission Result → Trade Record: contains trades
engine/SubmissionResult.h - TCP Server → Order Book API: prints book
server.cpp - Demo Operator → Scripted Book Demo: runs demo
README.md