...

Starting from FIXEdge v.5.12.0 there was added a business protection mechanism regulating incoming and outgoing traffic to optimize memory consumption and to prevent system from overloading. The mechanism includes control monitoring of throughput and of number of incoming messages received during a session as well as outgoing queue control monitoring for slow consumers protection detection.

Requirements

...

Features

• FIXEdge takes measurements to protect itself from higher throughput that may risk any part of the system overloading. Such incidents (i.e. of throughput higher than expected) must be reported and monitored

• The system must protect itself from slow consumers (i.e. by terminating slow consumers’ sessions)

• It are monitored and reported. It is essential that the incoming message flow will not exceed substantially the maximum daily expected number of messages from each inbound connection. It is possible to set:

  • The maximum number of messages per second a FIX session can send to FIXEdge

  • The maximum number of messages per day a FIX session can send to FIXEdge

• FIXEdge should provide FIXEdge protects itself from slow consumers by monitoring and reporting the sessions with larger outgoing message queue. FIXEdge provides monitoring and alerting functionality for the outbound queue in order to provide the support team with advanced notice of any possible threat to the system

• In case either threshold is reached, the FIX session will be logged out manually in order to prevent further messages from being sent.

...