System Map¶
Domain-level topology for NovaTrek Adventures — 22 services across 9 domains.
Everything on this portal is entirely fictional
NovaTrek Adventures is a completely fictitious company used as a synthetic workspace for the Continuous Architecture Platform proof of concept.
Domain Overview¶
Each node represents a domain (bounded context) containing one or more microservices. Arrows show cross-domain communication with connection counts.
Domains¶
Click a domain in the diagram or table to see its service-level topology with individual connections.
| Domain | Services | REST Out | Events Out |
|---|---|---|---|
| Booking | 1 | 4 | 3 |
| External | 1 | 5 | 0 |
| Guest Identity | 1 | 2 | 2 |
| Guide Management | 1 | 0 | 0 |
| Logistics | 2 | 6 | 0 |
| Operations | 2 | 13 | 4 |
| Product Catalog | 2 | 4 | 0 |
| Safety | 3 | 11 | 9 |
| Support | 9 | 5 | 1 |
Legend¶
| Element | Meaning |
|---|---|
| Blue box | Domain (bounded context) containing one or more services |
| Solid arrow with label | Synchronous REST calls (count shown) |
| Dashed purple arrow | Asynchronous Kafka events (count shown) |
How to Read This Diagram¶
- Each box is a domain — a bounded context owning a group of related microservices
- Arrows between domains show cross-boundary communication with the number of distinct service-to-service connections
- High fan-in domains (many arrows pointing in) provide shared platform capabilities — Guest Identity, Support
- Dashed lines indicate event-driven decoupling — the source domain publishes events without knowing the consumers
- Drill down into any domain via the Domain Views page to see individual service connections
Data Source¶
Generated from architecture/calm/novatrek-topology.json by portal/scripts/generate-topology-pages.py.