Catalog-Account Sync Block Architecture

Catalog and account data synchronize from core Aria to Aria Allegro. Below is a block architecture of the key components involved in catalog and account sync activities.

Summary of the block diagram:

1. Core Aria—Core Aria 
   1. Core Aria configures the Data Feed LOM subscription for the client. The data feed must be enabled (usually managed during client onboarding).
   2. Catalog and account activities trigger Data Feed events that publish the Data Feed LOM JSON to a Kafka topic.
2. Aria Allegro Sync Service—This service consumes messages from the Data Feed Kafka topic and performs these actions:
   1. Creates an activity log with the data feed LOM JSON for audit and reconciliation.
   2. Marks the activity log as IGNORED if the data feed is irrelevant. To reduce noise, review the data feed notification settings in Core Aria.
   3. Converts the JSON payload into the structure required by Aria Allegro.
   4. Uses a common library to call APIs that create Catalog and Account objects in the database.
   5. If the Data Feed LOM errors, the activity log status updates to Error with the reason. These records can be reprocessed once fixed. Common errors include:
      1. Kafka topic producer and consumer setup issues.
      2. Data Feed LOMs received out of order; reprocess after subsequent messages.
      3. Missing configuration in Aria Allegro. Core Aria Catalog sync needs configuration in Aria Allegro. Set configurations before reprocessing. Account data is view-only and requires no setup.
3. Allegro UI allows review and reprocessing of Account/Catalog sync activities.