Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed

Data stores

Every data technology the estate runs on, not just the shared SQL estate: MongoDB carries a large share of the cloud services, Redis is a second coupling plane, and DynamoDB and S3 underpin the payments and document platforms. Repos sharing a store are coupled even without a code edge. The three core SQL databases are binding points; stage 4 of the programme gives them named owners.

Repos using each technology

A repo can use several technologies. Click a bar to filter the stores below.

The shape of the data estate

SQL Server: 98 stores across 89 repos. The legacy centre of gravity, and where the shared-schema coupling lives.

MongoDB: 75 stores across 66 repos. The default operational store for the modern and cloud services, mostly one database per service, which is exactly the decoupled pattern the programme wants.

Redis: 11 stores across 46 repos. Caching, session state and streams; shared instances couple services as a second plane.

Amazon S3: 13 stores across 12 repos. Object storage for documents, assets and request logs.

DynamoDB: 8 stores across 6 repos. The payments platform's serverless store.

Azure Blob Storage: 1 store across 1 repo.

OpenSearch: 1 store across 1 repo.

Snowflake: 1 store across 1 repo.

Shared stores (7) — MongoDB

StoreTechnologyCoupled repos
mongodb:UserAccounts MongoDB4backoffice-useraccount-service, tc-performance, useraccount-api, viewing-as-api
mongodb:Gold MongoDB3tc-gold-api, useraccount-api, viewing-as-api
mongodb:Accommodation MongoDB2ibs-errata-api, phenix-accommodation
mongodb:Destinations MongoDB2phenix-destination-management, service-fee-api
mongodb:PackageValidation MongoDB2phenix-packagevalidation-api, tc-phenix-dynamicmargin
mongodb:TCCommissionStatements MongoDB2backoffice-commissions-service, commission-statements-api
mongodb:ViewingAs MongoDB2useraccount-api, viewing-as-api

Single-owner stores (68) — MongoDB

Owned by one repo each; no cross-system coupling. This is the healthy pattern most of the MongoDB estate follows.

mongodb:address_lookup_apimongodb:automatchapi_logsmongodb:AutomatchSupplierConfigurationmongodb:balanceduedateapi_logsmongodb:bookingCommissionRate_logsmongodb:BookingDataExportermongodb:bookingdownloadApi_logsmongodb:bookingGraphQL_logsmongodb:CarHireGateway_logsmongodb:CompanyInfomongodb:CoPilotmongodb:CostSavingsmongodb:Cruisemongodb:CruiseContentmongodb:CustomDataFieldsmongodb:cybersourceapi_logsmongodb:Dashboardmongodb:DefinitionStoremongodb:DestinationSearch_logsmongodb:DestinationsHangfiremongodb:DocumentDashboardmongodb:ExchangeRatesmongodb:FlightsTravelportJsonmongodb:ForecastPricingmongodb:GiftRegistrymongodb:gold_logsmongodb:honeymoonapi_logsmongodb:ibs_apimongodb:InsuranceAcl_Rock_Insurance_logsmongodb:InsuranceGateway_logsmongodb:itineraries_apimongodb:ledger_logsmongodb:Litmosmongodb:MailSchedulermongodb:MailTrackedmongodb:p2pGateway_logsmongodb:Permissionsmongodb:permissions_logsmongodb:PhenixBackOfficeIntegration_logsmongodb:PhenixMarketingmongodb:PhenixRetailmongodb:Placesmongodb:providerApi_logsmongodb:ProviderTransactionsmongodb:PublicFeaturesmongodb:PublicQuotemongodb:PublicReviewsmongodb:PublicTravelCounsellorsmongodb:PushNotificationsmongodb:ReasonsToCallmongodb:Referralsmongodb:ServiceFeemongodb:Taxmongodb:TCActionsmongodb:TcAuctionmongodb:TcItinerariesmongodb:TCPerformancemongodb:TcProfilesmongodb:Teamsmongodb:teams_logsmongodb:TemplateStoremongodb:Trainlinemongodb:traveloperations_d365_logsmongodb:travelprotection_logsmongodb:trustpaymentsapi_logsmongodb:vcc_conferma_api_logsmongodb:vcc_wex_logsmongodb:Vibe