Velaxe EventBus — Integration

Overview

Publish ProductCatalog domain changes so authorized consumers can react without polling catalogue tables.

Capabilities

• 44 published topics covering products, categories, collections, options, attributes, option media and promotion domains

• velaxe.context.changed invalidation topic

• Trusted caller and request provenance propagated for machine-initiated mutations

• Product view events separated from change invalidation

• No direct database coupling required for subscribers

1. 1

   Step 1

   Choose the ProductCatalog topics relevant to the consuming workflow.

   Back to top
2. 2

   Step 2

   Configure the consuming application through Velaxe event subscription mechanisms.

   Back to top
3. 3

   Step 3

   Process domain events using their source and request provenance.

   Back to top
4. 4

   Step 4

   Use velaxe.context.changed when cached context should be refreshed.

   Back to top

Limitations

• ProductCatalog is primarily an event producer and declares no app-owned event subscriptions.

• Event delivery does not replace operation authorization for direct ProductCatalog mutations.

FAQs

Pricing