| div |
|---|
|
| div |
|---|
| | Table of Contents |
|---|
| maxLevel | 2 |
|---|
| indent | 8px |
|---|
| style | none |
|---|
|
|
|
Overview
| Excerpt |
|---|
An AEPEngine handles processing of each inbound message it receives in an atomic fashion - the acknowledgement of message receipt, application changes to state and outbound messages constitute an atomic unit of work. Each such atomic unique of work is considered an AEP transaction. Transactions are, for the most part handled, transparently from an application's standpoint. Application developers simply write message handlers with the assurance the processing done therein will be atomic. |
The sections below This section discuss some of the ways that applications can influence or interact with AEP transactions. |
Adaptive Batching
By default an AEPEngine handles processing of each inbound message it receives as a single transaction. It is possible to configure an AEPEngine to attempt to batch up the processing of several inbound messages into a single transaction via a feature called adaptive batching. This feature can improve throughput at the cost of increased latency of outbound messages (the outbound messages for the first message processed in a batch won't be sent until the last message in the batch has been stabilized. The batching behavior is adaptive in nature because the engine commits a batch automatically when either a configured adapative batch ceiling is reached or the engine detects there are no more messages immediately available to process.
...
