Integrating events

The event integration helps you to deliver and publish the events to cloud storage solutions.

This page content applies to SaaS only. All the item-related changes lead to computing availability and trigger the event message. Examples of item-related changes are configuration changes (such as updates to safety stock, fulfillment options, changes in parent-child relationship), transaction-related changes, or bulk actions such as DG sync.

Note: The IBM Cloud® Object Storage provides a stable data store base with high availability and low-cost storage. However, webhooks requires to expose REST endpoint and provide resiliency of the servers and backup policy to ensure ongoing event consumption handling.
Table 1. Comparative analysis for webhooks and COS
Characteristics Webhooks IBM Cloud Object Storage
Description Events are pushed to a client's REST webhook. Events are pushed to IBM Cloud Object Storage and you need to download from IBM Cloud Object Storage to process the data.
Configuration Configure a webhook to support OAuth2 authentication. Configure an account on the IBM Cloud Object Storage service.
Scalability Webhook needs to scale up as needed. Ability to scale up with different tiers.
Potential issues Need to implement a pull process to retrieve failed events. Need to implement a pull process to retrieve failed events.
Data loss Data loss can happen if pull process is not implemented. Data loss can happen if pull process is not implemented.
Hosting Hosted by customer Hosted by IBM Cloud
Setup Hosted by customer Hosted by IBM Cloud
Costs Customer-side hosting Customer paid storage
Storage Customer-owned Offered as a part of COS service
Event processing Receive inbound webhook data Downloads files and process
Event delivery format Single event per message (Legacy)
Variable size array (event type and data dependent)		 Batched message per file (up to 1000 events)
Ideal for Change events Change and snapshot events
Event subscription requirements
  • Client provides the OAuth and Rest Endpoints with millisecond API response time
  • Process events on receipt
  • Respond to POST calls efficiently
 Download storage data and delete or archive on success
Error rate Varies on client implementation Less than 0.5%