Events

An event records that something happened, so that other code can react to it later without the action that caused it waiting.

An action announces an event with emit, a statement written like reject (Raising a failure).

A subscriber reacts to an event: each time the event is committed, it runs an action.

In an app with a tenant:, each kind of background work reaches a stated set of tenants.

One domain changes another in one of two ways (Ownership and calls replace modules): it calls one of the other domain's public actions, or it emits an event the other domain subscribes to.

A process that waits for several things over time, such as an order waiting for both payment and stock, needs no workflow language.

Events stay inside the Jadpo runtime.

Besides the events your actions emit, four sources outside the app produce events: webhooks, a package's own events, polls and queues.