Event Routing insures a higher data throughput by providing a method for sending events asynchronously. When an asynchronous send operation is performed, Event Routing queues the event for further processing, but does not wait for the queue to be synchronized with the disk, even in case any of the destination services are set to reliable via the Command Central user interface, thus making it possible for the next send operation to be executed faster. When an asynchronous send operation is invoked, the calling application must provide a callback, which Event Routing then uses to notify the application when the event has been queued and, in case of a reliable destination service, the queue has been synchronized with the disk.

You can also send events synchronously using the respective Event Routing method in your applications. In case a synchronous send operation is performed, and the destination service is set to reliable via the Command Central user interface, Event Routing queues the event for processing and synchronizes the queue with the disk before processing the next send operation. In this case, the throughput of events is slower.