Services Catalog

6 bounded contexts extracted via Domain-Driven Design. Each service owns its data and communicates through well-defined interfaces.

Context Map

Solid lines = synchronous (ACL), dashed = async events via Service Bus.

Core Domain

Travel Booking

planned

Handles all travel booking operations including itineraries, supplier integrations, and pricing. The highest-value core domain with the most complex business rules.

Context: Travel

Database: Azure SQL — Travel DB (bookings, itineraries, suppliers, pricing tables)

Owner: D2

Go-live: M3

Phase 1

Event Management

planned

Manages events, venues, schedules, and attendees. Complex scheduling logic with venue capacity constraints and multi-day event support.

Context: Events

Database: Azure SQL — Event DB (events, venues, schedules, attendees tables)

Owner: D3

Go-live: M4

Phase 1

Supporting

Workforce + Allocation

planned

Manages staff profiles, skills, shift allocations, and availability. Subscribes to Travel and Event domain events to coordinate staffing needs.

Context: Workforce

Database: Azure SQL — Workforce DB (staff, allocations, shifts, skills tables)

Owner: D4

Go-live: M6

Phase 2

Reporting (CQRS)

planned

Read-only reporting service using CQRS pattern. Aggregates data from all services via CDC and event projections to build cross-module dashboards and reports.

Context: Reporting

Database: Azure SQL — Reporting DB (materialized views, read models, CDC replicas)

Owner: D5

Go-live: M7

Phase 2

Generic

Communications

planned

Cross-cutting notification service handling email, SMS, and push notifications. Subscribes to ALL domain events across the system to trigger appropriate communications.

Context: Comms

Database: Azure SQL — Comms DB (templates, notification logs, delivery status)

Owner: D4

Go-live: M7

Phase 2

Service Comparison

Service	Owns	Key APIs	Communication	DB
Travel Booking	bookings, itineraries, suppliers, pricing rules	/api/travel/*	Sync REST (client-facing) + Payment ACL (sync to legacy) + Async events (BookingCreated, BookingCancelled)	Azure SQL — Travel DB (bookings, itineraries, suppliers, pricing tables)
Event Management	events, venues, schedules, attendees	/api/events/*	Sync REST + Payment ACL (sync to legacy) + Async events (EventCreated, AttendeeRegistered)	Azure SQL — Event DB (events, venues, schedules, attendees tables)
Workforce + Allocation	staff profiles, allocations, shifts, skills	/api/staff/*	Subscribes to travel/event events (StaffNeeded, EventStaffed) + Sync REST for staff queries	Azure SQL — Workforce DB (staff, allocations, shifts, skills tables)
Communications	notifications, templates, delivery logs	/api/comms/*	Subscribes to ALL domain events (BookingCreated → send confirmation, EventReminder → send email, etc.)	Azure SQL — Comms DB (templates, notification logs, delivery status)
Reporting (CQRS)	report definitions, read models, dashboards	/api/reports/*	CDC from all service databases + Event projections from Service Bus	Azure SQL — Reporting DB (materialized views, read models, CDC replicas)
Payment (Legacy)	payments, invoices, reconciliation	/api/payments/* (via ACL bridge)	ACL adapter pattern — new services call a clean interface that translates to legacy API format	Legacy SQL Server (shared monolith DB) — payment, invoice tables