- product-portfolio
- ecosystem-catalog
- deep-dives
- vertical
Hospitality, Travel, Events & Local Services - Analysis¶
Planning-layer analysis for category 25. It groups the 50 candidate services into capabilities, recommends what becomes a standalone service versus a module, and captures domain, interface, and non-functional notes. For the plain item list see the browse page.
Scope & Bounded Context¶
- Primary bounded context: Hospitality & Travel
- Group: vertical
- Default wave / cycle: Phase 5 · Cycle 5: Marketplace & Ecosystem
- Items: 50 candidates
This category is anchored to the ConnectSoft DDD baseline in the SaaS framework DDD blueprint and the service classification model.
Classification Breakdown¶
| Classification | Count |
|---|---|
| Module-in-service | 43 |
| Platform Product | 5 |
| Portal/UI Module | 2 |
Anti-fragmentation stance
Per ADR-0011, the 43 module candidates below are delivered inside the Hospitality & Travel bounded-context service, not as separate microservices. Only the 5 platform/service candidates justify an independent runtime.
Standalone Service / Platform Candidates¶
| ID | Service | Tier | Status |
|---|---|---|---|
| CS-SVC-1201 | Hotel Property Management System | 4 | Planned |
| CS-SVC-1203 | Guest Experience Platform | 4 | Planned |
| CS-SVC-1204 | Restaurant Operations Platform | 4 | Planned |
| CS-SVC-1205 | Travel Booking Platform | 4 | Planned |
| CS-SVC-1231 | Local Services Booking Platform | 4 | Planned |
Portal / UI Modules¶
- Service Provider Portal (
CS-SVC-1233) - Reputation Dashboard (
CS-SVC-1237)
Domain, Interfaces & Data Ownership¶
- Aggregates are owned by the Hospitality & Travel context; cross-context reads go through published contracts, never shared databases.
- Integration is event-first (outbox + integration events) per the event-driven mindset.
- APIs are contract-first and versioned through the API & Integration context.
Non-Functional Posture¶
- Multi-tenancy & edition-awareness: required for all serious candidates.
- Security: Standard baseline; secrets via the platform secret store; least privilege.
- Compliance: standard audit logging.
- Observability: OpenTelemetry traces, metrics, and structured logs.
MVP vs Future¶
- MVP (Tier 0-1): see roadmap
- Future (Tier 4-5): Hotel Property Management System, Reservation Management Service, Guest Experience Platform, Restaurant Operations Platform, Travel Booking Platform, Room Inventory Service, Rate Management Service, Channel Manager Integration
Open Questions¶
- Which module candidates, if any, develop independent scaling or ownership needs that would justify promotion to a standalone service?
- Where do this category's contracts overlap with adjacent contexts, and who owns them?