Appendix B - Architectural Diagrams
Simple architectural diagrams of the BOEv3 port deployments.
Note that members using BOEv3u ports interact directly with the BOEv3u process, however a separate TCP connection is required for each unit.
BOEv3u Ports provide an expedited processing path to the Matching Engine over that of other inbound paths on a best effort basis. Under routine circumstances, the System will process pending purge messages from BOEv3u ports before processing other inbound paths. Exceptions to this approach exist with regard to various flow control and rate limiters that are incorporated into the mechanism.
Example of the Processing under routine circumstances:
Process pending purge messages from BOEv3u ports within a bounded network window
Process all other pending messages from BOEv3u ports, not to exceed bounded network window from step 1
Process pending messages from Convenience ports, not to exceed bounded network window from step 1
C1, C2, and EDGX Options Exchanges are set up with all port types residing in a "convenience" style architecture. All ports have access to all Matching Units. All customer messaging is processed at the Matching Engine in the order that it arrives at each Matching Engine NIC.