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 (26) — SQL Server

StoreTechnologyCoupled repos
sqlserver:Phenix core databaseSQL Server22backoffice-receipt-service, backoffice-repository-service, phenix-accommodation, phenix-attractions, phenix-cms, phenix-database and 16 more
sqlserver:EventLog core databaseSQL Server14backoffice-eventlog, backoffice-pure360-marketing-service-api, backoffice-pure360-subscription-manager, mail-service, phenix-cruise-service, phenix-flights and 8 more
sqlserver:ContactCentre core databaseSQL Server9TC.CustomerPortalUsers.DupeImporter, contact-centre-email-server, intranet, phenix-contact-api, phenix-contact-centre-2-api, phenix-contact-centre-api and 3 more
sqlserver:MediaServer SQL Server5admin-studio, backoffice-customerrelations-ui, intranet, phenix-contact-centre-web, phenix-retail
sqlserver:TravelCounsellors SQL Server5TC.PublicWebsites.EmailQueue, intranet, phenix-tcselfservice-api, public-api, travelcounsellors-net
sqlserver:DataWarehouse SQL Server4admin-studio, alert-management, intranet, phenix-contact-centre-2-api
sqlserver:Accounts SQL Server3backoffice, booking-tags-api, intranet
sqlserver:CustomerPortal SQL Server3mytc-user-service, phenix-honeymoon-api, tc-gift-registry
sqlserver:UserAccount SQL Server3backoffice-useraccount-service, phenix-user-api, tc-useraccount-telephonecontracts-api
sqlserver:VirtualCreditCard SQL Server3vcc-service, vccprovider-enett, vccprovider-wex
sqlserver:AttractionsRepository SQL Server2phenix-attractions, phenix-provider-databases
sqlserver:CommissionService SQL Server2backoffice-commissions-service, intranet
sqlserver:ContactApi1 SQL Server2backoffice-pure360-marketing-service-api, backoffice-pure360-subscription-manager
sqlserver:DestinationManagement SQL Server2phenix-destination-management, scheduled-tasks
sqlserver:DirectStockAccommodationContract SQL Server2direct-stock, phenix-passenger-service
sqlserver:HotelsDesertAdventures SQL Server2phenix-accommodation, phenix-provider-databases
sqlserver:IntranetMIS SQL Server2db-intranet-mis, intranet
sqlserver:Location SQL Server2phenix-linking-service, scheduled-tasks
sqlserver:Repository SQL Server2backoffice-repository-service, phenix-root
sqlserver:Reviews SQL Server2phenix-reviews, tc-reviews-sync-service
sqlserver:tcdb SQL Server2intranet, tc-communications
sqlserver:TCDB SQL Server2phenix-tcselfservice-api, travelcounsellors-net
sqlserver:Teams SQL Server2intranet, teams-service
sqlserver:Transfers SQL Server2phenix-p2p, phenix-provider-databases
sqlserver:Ttand SQL Server2phenix-contact-api, ttand-database
sqlserver:TTIGIATAData SQL Server2phenix-provider-databases, scheduled-tasks

Single-owner stores (72) — SQL Server

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

sqlserver:AccommodationConfigurationsqlserver:AccountsArchivesqlserver:AddressLookupsqlserver:AlertManagementsqlserver:AssetManagementsqlserver:AttractionsDoSomethingDifferentsqlserver:AttractionsMusementsqlserver:AuditDirectStockAccommodationContractsqlserver:AutoMatchDatabasesqlserver:BlogLocationsDatabasesqlserver:BookingCommissionRatesqlserver:BookingDocumentationsqlserver:CardPaymentsDatabasesqlserver:CarHiresqlserver:CarHireAVISsqlserver:CarHireDepotssqlserver:CarHireEHIsqlserver:CarHireFlexibleCarHiresqlserver:CarHireRepositorysqlserver:CarHireSunnyCarssqlserver:Competitionssqlserver:Conferencesqlserver:crmreporting (Azure SQL, aznesqlrecruitmentprod)sqlserver:CruiseTravelTeksqlserver:CustomerRelationssqlserver:Cybersourcesqlserver:DestinationSearchsqlserver:DirectStockGroundHandlingContractsqlserver:DirectStockTransferContractsqlserver:DocumentationCertificatesTasksqlserver:Documentssqlserver:EventLogArchivesqlserver:ExchangeRateRepositorysqlserver:Flightssqlserver:FlightsConfigurationsqlserver:GidsExtensionssqlserver:GroundHandlingsqlserver:HotelsBonotelsqlserver:HotelsGalileosqlserver:HotelsHotelBedssqlserver:HotelsJacobsTravelsqlserver:HotelsJumeirahsqlserver:HotelsMedHotelssqlserver:HotelsMulticomsqlserver:HotelsNightsBridgesqlserver:HotelsSwapSystemssqlserver:HotelsTravcosqlserver:HotelsW2Msqlserver:HotelsWebBedssqlserver:Ledgersqlserver:MarketingDatasqlserver:MediaManagementsqlserver:OperationalDataStoresqlserver:PaymentChecksqlserver:ProviderArabianAdventuressqlserver:ProviderMrAndMrsSmithsqlserver:ProviderResortMarketingsqlserver:Pure360MarketingCampaignssqlserver:Quotesqlserver:Recruitmentsqlserver:Supplierssqlserver:TaskRemindersqlserver:Tcdbsqlserver:TransfersHolidayTaxissqlserver:TransfersResortHoppasqlserver:TransferStagingsqlserver:TravelCounsellorWebDetailsqlserver:TrustPaymentssqlserver:TrustYousqlserver:UserAccount_Legacysqlserver:vcc_api_logssqlserver:VccProviderConferma