Abstract: Guaranteed, exactly once delivery of messages is disclosed. In one embodiment, there is a sender and a receiver. In a sender transaction, the sender does the following: receives a message from a sender queue; generates a substantially unique identifier and an expiration time for the message; and, saves the identifier, the expiration time, and the message in a sender database. The sender then sends the identifier, the expiration time, and the message to the receiver. In a receiver transaction, the receiver then does the following: receives the identifier, the expiration time, and the message from a receiver queue; determines whether the message has expired based on the expiration time and determines whether the message is present in a receiver database by its identifier; and, upon determining that the message has not expired and is not present in the receiver database, stores the message in the receiver database, and performs actions associated with the message.

Abstract: Automatic message-based module invocation within a transactional message system is described. The modules can be software components, executable program files, etc. In one embodiment, a system includes one or more queues, a trigger store, and a trigger service. Each queue is capable of receiving messages. The trigger store includes one or more triggers, where each trigger is associated with a queue, and has associated therewith one or more rules, where each rule has a condition and an action. The trigger service is designed to, upon receipt of a message in a queue, check the condition of each rule of each trigger associated with the queue, to determine if the message satisfies the rule's condition. If such satisfaction occurs, then the action of the rule is performed, which can include invocation of a module. The rules may be short-circuit rules, non-destructive rules, and/or destructive rules, and may be checked in either a concurrent or serial manner.