Event Catalog¶
Domain Events Published and Consumed Across NovaTrek Services
9 Events · 8 Producers · 8 Consumers
The NovaTrek platform uses Apache Kafka as its event bus for asynchronous inter-service communication. Each event is published to a dedicated channel and consumed by one or more downstream services.
Event Flow Overview¶
This overview shows which domains produce and consume events through the Kafka event bus. Drill into each domain section below for service-level detail.
Generated from architecture/metadata/events.yaml
Operations¶
Generated from architecture/metadata/events.yaml
| Event | Channel | Producer | Consumers | Schema |
|---|---|---|---|---|
| checkin.completed | novatrek.operations.checkin.completed | svc-check-in | svc-analytics, svc-notifications | |
| schedule.published | novatrek.operations.schedule.published | svc-scheduling-orchestrator | svc-guide-management, svc-notifications |
Guest Identity¶
Generated from architecture/metadata/events.yaml
| Event | Channel | Producer | Consumers | Schema |
|---|---|---|---|---|
| guest.registered | novatrek.guest-identity.guest.registered | svc-guest-profiles | svc-loyalty-rewards, svc-analytics |
Booking¶
Generated from architecture/metadata/events.yaml
| Event | Channel | Producer | Consumers | Schema |
|---|---|---|---|---|
| reservation.created | novatrek.booking.reservation.created | svc-reservations | svc-scheduling-orchestrator, svc-analytics | |
| reservation.status_changed | novatrek.booking.reservation.status-changed | svc-reservations | svc-notifications, svc-analytics |
Safety¶
Generated from architecture/metadata/events.yaml
| Event | Channel | Producer | Consumers | Schema |
|---|---|---|---|---|
| emergency.triggered | novatrek.safety.emergency.triggered | svc-emergency-response | svc-notifications, svc-scheduling-orchestrator, svc-safety-compliance, svc-analytics | |
| incident.reported | novatrek.safety.incident.reported | svc-safety-compliance | svc-notifications, svc-analytics | |
| wildlife_alert.issued | novatrek.safety.wildlife-alert.issued | svc-wildlife-tracking | svc-notifications, svc-scheduling-orchestrator, svc-trail-management, svc-analytics |
Support¶
Generated from architecture/metadata/events.yaml
| Event | Channel | Producer | Consumers | Schema |
|---|---|---|---|---|
| payment.processed | novatrek.support.payment.processed | svc-payments | svc-reservations, svc-notifications |
Event Details¶
checkin.completed¶
- Channel:
novatrek.operations.checkin.completed - Producer: svc-check-in
- Trigger:
POST /check-ins - Domain: Operations
- Description: Published when a guest completes the check-in process
- Schema: View Event Schema
Consumers:
emergency.triggered¶
- Channel:
novatrek.safety.emergency.triggered - Producer: svc-emergency-response
- Trigger:
POST /emergencies - Domain: Safety
- Description: Published when a new emergency SOS is triggered by a guest or staff member
- Schema: View Event Schema
Consumers:
guest.registered¶
- Channel:
novatrek.guest-identity.guest.registered - Producer: svc-guest-profiles
- Trigger:
POST /guests - Domain: Guest Identity
- Description: Published when a new guest profile is created
- Schema: View Event Schema
Consumers:
incident.reported¶
- Channel:
novatrek.safety.incident.reported - Producer: svc-safety-compliance
- Trigger:
POST /incidents - Domain: Safety
- Description: Published when a safety incident is reported
- Schema: View Event Schema
Consumers:
payment.processed¶
- Channel:
novatrek.support.payment.processed - Producer: svc-payments
- Trigger:
POST /payments - Domain: Support
- Description: Published when a payment is successfully processed
- Schema: View Event Schema
Consumers:
reservation.created¶
- Channel:
novatrek.booking.reservation.created - Producer: svc-reservations
- Trigger:
POST /reservations - Domain: Booking
- Description: Published when a new reservation is confirmed
- Schema: View Event Schema
Consumers:
reservation.status_changed¶
- Channel:
novatrek.booking.reservation.status-changed - Producer: svc-reservations
- Trigger:
PUT /reservations/{reservation_id}/status - Domain: Booking
- Description: Published when a reservation status transitions
- Schema: View Event Schema
Consumers:
schedule.published¶
- Channel:
novatrek.operations.schedule.published - Producer: svc-scheduling-orchestrator
- Trigger:
POST /schedule-requests - Domain: Operations
- Description: Published when a daily schedule is finalized
- Schema: View Event Schema
Consumers:
wildlife_alert.issued¶
- Channel:
novatrek.safety.wildlife-alert.issued - Producer: svc-wildlife-tracking
- Trigger:
POST /alerts - Domain: Safety
- Description: Published when a dangerous wildlife alert is issued for trails in a region
- Schema: View Event Schema
Consumers:
AsyncAPI Specifications¶
Each producing service has an AsyncAPI 3.0 specification file describing its published events in detail.