[Exchange-1.1] Uniform IPC Messaging Interface #10

As a backend engineer working on exchange services (Gateway, Sequencer, Matching Engine)
I want a uniform, strongly-typed inter-process messaging interface that allows services to construct, serialize, and parse messages using a common message type and field-based API
So that all services can communicate over shared memory or other IPC mechanisms in a consistent, versionable, and low-latency manner without hard-coupling to each other’s internal data structures.