Abstract
The present technology provides an asynchronous task messaging service for a server that supports near real-time communications. The asynchronous task service, as a cloud-based message-oriented middleware, sends messages associated with the tasks back to the community hosting service. A delay is encoded in the task code of the message that sets a delay mechanism that is custom to the task and task code. The tasks sent to the asynchronous task service includes tasks that only need to be executed within a reasonable amount of time (i.e., within a couple of days), tasks that need to be executed as soon as possible but does not make sense after a certain amount of time, and tasks that need to execute with as much effort as is reasonable to happen exactly once.