pcs-add-kafka-event

To add a new Kafka event, define the topic using the pcs.<domain>.<entity>.<action> convention, implement the emitter function, register the consumer handler, and initialize the consumer before the service starts.

PCS Kafka topics must follow the pcs.<domain>.<entity>.<action> format. This standardized naming ensures proper event catalog inclusion and cross-service contract compatibility within publish/subscribe scenarios.

TenantScope provides context management for consumer handlers to ensure proper tenant isolation. It guards the handler execution flow so that event processing remains securely scoped to the correct tenant.

Publishing a Kafka event requires an emitter function that includes specific metadata: request_id, org_id, timestamp, and source_service. This metadata ensures proper event tracing and cross-service contract fulfillment.

To prevent missing Kafka events, you must guarantee startup-order by registering the consumer and completing pre-start registration before the service begins. This ensures the handler is active before events are emitted.

Yes, the consumer setup establishes idempotent consumers to safely handle event retries. This prevents duplicate processing and maintains data consistency across cross-service domains during publish/subscribe operations.