Event Sending Strategies - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

The Alfresco repository supports strategies for sending events.

To select a strategy, set the repo.event2.send.strategy property to one of the following values:

Note: Ensure you select the right strategy based on your needs and requirements.
Strategy Delivery Mode Description
async At most once: events can be lost An event is queued in the memory and sent asynchronously to the broker.

The default behavior in the Community Edition of Content Services.

direct At most once: events can be lost An event is sent directly to the broker after the transaction that caused it.
outbox At least once: duplicates might occur An event is queued in the database as part of the same transaction that caused it. Events are sent asynchronously, with possible retries.

The default behavior in the Enterprise Edition of Content Services, and not available in the Community Edition.

If this strategy is used, a user has access to the following metrics:

  • outbox-queue-size - the number of events, in the database queue, waiting to be sent to the broker.
  • outbox-queue-lag - the waiting time (in milliseconds) for the oldest event in the queue.
  • outbox-event-stored - the count and duration of storing a single event.
  • outbox-event-processed - the count and duration of sending a single event to the broker.
  • outbox-batch-processed - the count and duration of dealing.