Leverage Adobe I/O Events retry mechanism for application resilience
The video outlines a comprehensive guide on leveraging Adobe I/O Events’ built-in retry mechanism to enhance application resilience. Learn how specific HTTP response status codes trigger event retries. Adobe I/O Events employs exponential and fixed back-off strategies for retries, with intervals increasing from one minute to 15 minutes. The documentation also details how retry indicators appear in the developer console, with visual cues like warning icons and circular arrows denoting failed and retried events, respectively.
Learn how the retry mechanism functions within the context of the ‘consumer’ runtime actions, and determine whether an event is retried. Successful responses are indicated with a 200 status code, while error responses include an error object with a ‘statusCode’ attribute. The ‘consumer’ runtime action determines the HTTP response code to return based on downstream processing outcomes, ensuring efficient event handling and eventual successful activations.
Audience
- Developers who want to understand the specific HTTP response status codes that trigger event retries.
- Teams who want to learn about the exponential and fixed back-off strategies employed by Adobe I/O Events for retries.
- Developers who want to understand how visual indicators in the developer console represent failed and retried events.
Video dontent
- Adobe I/O Events have a built-in out-of-the-box retry mechanism that automatically retries event activations based on specific HTTP response status codes.
- The retry mechanism implemented by Adobe I/O Events involves exponential and fixed back-off strategies.
- Visual indicators in the developer console, such as warning icons for failed events and circular arrow icons for retried events.
- The ‘consumer’ runtime actions play a crucial role in determining the appropriate HTTP response status codes for event handling.