Instead of directly delivering each event to the configured destination services and waiting for each service to acknowledge the event, Event Routing stores the event in an internal queue. Depending on the reliability setting defined for each destination service via the Command Central user interface, the queue can be held in-memory or on disk. Once an event is added to the queue, Event Routing is ready to accept new events. In the meantime, the queued events are delivered to their destination services by a separate thread in the order in which they were added to the queue.