CORE platform

reference architecture · draft for review

A layered map of the CORE platform: how a request travels from the client edge through the application APIs into CORE's capability domains, and out to datastores and downstream systems. Click any box to expand its endpoints, dependencies, and integration note.

Capability domain endpoints — sourced from the CORE Swagger spec
Updated at: 14.09.2026

End-to-end journeys through CORE, reconstructed from the endpoint dependency data. Each step names the CORE domain and the downstream system it hits. Click a step to expand the call detail. These sequences are inferred and marked for team validation.

Full service map: all 25 CORE capability domains with their infrastructure dependencies (solid edges) and cross-domain Lambda invocations (dashed edges). Generated from the same endpoint dependency data as the Architecture tab, cross-checked against it to keep both views consistent.

👆 Click a service to highlight its integrations
Scroll to pan · buttons to zoom · click a node to isolate its integrations
CORE CORE platform — full service map cluster_client Client cluster_edge Edge cluster_private Private microservices cluster_core CORE microservices cluster_ext External integrations cluster_data Data layer cluster_async Async & compute cluster_public Public microservices cluster_admin Admin microservices Client Client devices CF AWS CloudFront Azure Azure CDN APIGW API Gateway Client→CF Client devices→Azure CF→APIGW Addons Addons APIGW->Addons Air Air APIGW->Air Alerts Alerts APIGW->Alerts Auth Auth APIGW->Auth Calendar Calendar APIGW->Calendar Cart Cart APIGW->Cart Cities Cities APIGW->Cities Converter Converter APIGW->Converter Dining Dining APIGW->Dining Email Email APIGW->Email Excursions Excursions APIGW->Excursions Extensions Extensions APIGW->Extensions Forms Forms APIGW->Forms Offercodes Offercodes APIGW->Offercodes Passengers Passengers APIGW->Passengers Places Places APIGW->Places Pricing Pricing APIGW->Pricing Search Search APIGW->Search SearchAgg Search aggregator APIGW->SearchAgg Spa Spa APIGW->Spa Staterooms Staterooms APIGW->Staterooms Stateroomspc Stateroomspc APIGW->Stateroomspc Tokenex Tokenex APIGW->Tokenex Travelagents Travelagents APIGW->Travelagents Voyages Voyages APIGW->Voyages Wallets Wallets APIGW->Wallets Evolution Evolution API (SOAP/REST booking engine) Addons->Evolution Air->Evolution DA DA service API (ABE — air) Air->DA CRM CRM/IDR · MXP (Guest & onboard) Passengers->CRM Spa->CRM Voyages->CRM GoogleAPI Google API Air->GoogleAPI Redis Redis Air->Redis Dynamo DynamoDB Air->Dynamo KafkaQ Kafka Air->KafkaQ Alerts->Redis Auth->Email invokes Auth->Passengers invokes Auth->Pricing invokes Cognito Cognito Auth->Cognito Lambda AWS Lambda Auth->Lambda Calendar->Redis Calendar->Dynamo Aurora Aurora DB Cart->Passengers invokes Cart->Evolution Cart->Lambda Cities->Redis ImageMagick imagemagick Converter->ImageMagick AdobePDF adobe.pdfservices Converter->AdobePDF Dining->Evolution SourceToad SourceToad Dining->SourceToad Dining->Redis CMS CMS Email->CMS FreshAddress freshaddress Verifly Verifly S3 S3 Passengers->Verifly Converter->S3 Email->FreshAddress Excursions->Evolution MSSql MSSql Extensions->MSSql Forms->MSSql Offercodes->Evolution Offercodes->Redis Passengers->Air invokes Passengers->Alerts invokes Passengers->Evolution Passengers->SourceToad Passengers->Redis Passengers->MSSql Passengers->Lambda SQSQ SQS Passengers->SQSQ Places->GoogleAPI Pricing->Voyages invokes Pricing->Evolution Pricing->Redis Pricing->MSSql Pricing->Lambda SearchAgg->Staterooms invokes SearchAgg->Voyages invokes Spa->SourceToad Spa->Redis Staterooms->Voyages invokes Staterooms->Evolution Staterooms->Redis Voyages->Evolution Voyages->Redis Voyages->Lambda Public Passengers Public Passengers Public Travelagents Public Travelagents China/Generic China/Generic Admin Admin APIGW->Public Travelagents APIGW->Admin Public Travelagents->Evolution China/Generic->Evolution Azure->China/Generic APIGW->Public Passengers Public Passengers->Evolution Admin->Lambda Admin->SQSQ Admin->KafkaQ Admin->Redis Admin->Dynamo Admin->Aurora Admin->CF APIGW->Cruises APIGW->Feed APIGW->Gifts Cruises->Redis Cruises->CMS Feed->Redis Feed->CMS Feed->Evolution Gifts->Redis Gifts->Evolution Addons->Redis Cruises Cruises Feed Feed Gifts Gifts Public Passengers->ParamStore Public Travelagents->ParamStore Admin->ParamStore Travelagents->ParamStore Wallets->ParamStore Extensions->ParamStore Forms->ParamStore Calendar->ParamStore Cities->ParamStore Converter->ParamStore Dining->ParamStore Addons->ParamStore Excursions->ParamStore Offercodes->ParamStore Cart->ParamStore Places->ParamStore Auth->ParamStore Search->ParamStore Spa->ParamStore SearchAgg->ParamStore Stateroomspc->ParamStore Tokenex->ParamStore Cruises->ParamStore Feed->ParamStore Gifts->ParamStore Email->ParamStore Pricing->ParamStore Passengers->ParamStore Staterooms->ParamStore Alerts->ParamStore Voyages->ParamStore Air->ParamStore Calendar->Aurora Cart->Aurora Wallets->Aurora Azure->EvoAir EvoAir->KeyVault EvoAir->KafkaQ EvoAir->Pricing EvoAir->DA Azure->CMSExport CMSExport->KafkaQ CMSExport->CMS China/Generic->KeyVault ParamStore Parameter Store KeyVault Key Vault CMSExport CMS Export EvoAir Evo Air Services

CI/CD build & deploy pipeline for the CORE platform: how each capability domain flows from its GitHub repository through the build stage into AWS runtime (Lambda / Step Functions), then is exposed via API Gateway and CloudFront to clients. Domains are derived from the same capability data as the Architecture tab; repository names follow the vrc_core_* convention. Optionally load the live repository list from the viking-cruises org (uses your GitHub token in the browser).

GitHub → Build (Actions) → Artifact (S3) → Provision (Terraform) → AWS runtime (Lambda / Step Functions) → API Gateway → CloudFront → Client Repos loaded: 14.09.2026

CORE repositories deployment status by environment. Click a repository row to expand details for each environment.

CORE — Cache build status per repository & environment
Refreshed: 14.09.2026

Deployed API Gateway integrations and Lambda log groups across CORE environments. This configuration snapshot is refreshed when the site is published.

The integration report could not be loaded.

Where this stands against the ticket

The structural map and one end-to-end flow are drafted from the existing image and the Core API methods PDF. What remains is human knowledge the sources don't hold — which flows count as "major," what "system boundaries" means, and sign-off. Each acceptance criterion below expands to its status and the question that unblocks it.