FIX-SBE combines institutional FIX session behavior with fixed-layout binary application messages. It is separate from tag-value FIX Classic and SBE WebSocket.
When to use FIX-SBE
Use FIX-SBE when your integration can:
- operate persistent trading sessions
- implement sequence, heartbeat, resend, and recovery behavior
- generate and validate versioned SBE messages
- complete protocol conformance and certification
Use FIX Classic when compatibility with tag-value FIX tooling is more important than binary application encoding.
Integration flow
Review the session package
Confirm the session protocol, schema identity and version, endpoint, authentication method, enabled business workflows, and operational limits.
Generate and validate codecs
Generate codecs from the assigned schema. Validate schema identity, template identity, block length, and version before decoding application messages.
Implement session behavior
Implement authentication, heartbeat, sequence persistence, resend, reconnect, and recovery according to the session profile.
Complete certification
Run the assigned protocol, compatibility, and recovery cases before connecting the production session.
Recovery boundaries
Persist protocol sequence and follow the session profile's resend and reset policy. Validate schema version again after reconnecting.
Session recovery does not necessarily provide a complete trading snapshot. Reconcile application state through the assigned FIX workflow or Polyester read APIs.
See the Connectivity matrix to compare FIX-SBE with ConnectRPC and SBE WebSocket.