Platform Events

Services communicate change across the Packt Platform by emitting events. This page describes the public events that are part of the platform's contractual boundaries and how to consume them safely.

Public vs Internal Events

Public event names use the packt.* prefix. Internal event names use the internal.* prefix. Do not integrate with another service's internal events — they can change at any time.

Event Naming Convention

Public event names follow a dot-separated structure:

1. packt (fixed)
2. service — e.g. content, products, distribution
3. resource — e.g. document, product, pricing, channel
4. version — e.g. v1
5. action — e.g. created, updated, deleted, published

Examples: packt.content.document.v1.created, packt.products.pricing.v1.updated.

Event Envelope

Event payloads use the CloudEvents envelope. The event type attribute is the event name above. The data payload is defined per event and may be JSON or protobuf. Consume by event type and version so payloads can evolve without breaking subscribers.

Transport

Public events are published to AWS EventBridge buses. Attach targets (Lambdas, SQS, other buses) by event name or pattern.

Best Practices

• At-least-once delivery — events may be delivered more than once. Handle idempotency using the event ID.
• Cross-service reactions only — use public events to react to changes in other services, not your own.
• Do not depend on internal events — if you need a public event that does not exist yet, request it.

Event Catalogue

Content Lake

Product Management

Distribution