KafkaEvents
Sovereign Physical Distribution Platform · Cluster Node
Protobuf and JSON Schema envelope definitions for all asynchronous domain events published across the Pegasus cluster.
All internal microservices and data pipelines communicate asynchronously via Kafka topics. To prevent contract drift, schemas are validated against a central Schema Registry with backward compatibility checks enforced in CI/CD.
Architecture & Performance Highlights
Strict Envelope Structure
Standard CloudEvents-compliant metadata header with trace_id, producer, and timestamp.
Zero Schema Drift
Backward-compatible Protobuf and JSON schemas prevent producer/consumer contract breakages.
Dead-Letter Queues (DLQ)
Poison pill messages automatically route to designated DLQs with automated alerting and replay tooling.
Partition Keying Law
Always specify the partition key as supplier_id or warehouse_id. Never publish order events without a partition key, as unordered processing will break state machines.
Keep Exploring Pegasus Architecture & Operations
Based on the invariants, physical actors, and data flows of this module, explore these recommended companion guides and operational playbooks.
Transactional Outbox & Bus
Learn how the Go outbox daemon pulls events from the database and produces to these Kafka topics.
WebSocket Event Hub
The WebSocket hub acts as a high-speed Kafka consumer bridge to front-end web and mobile applications.