Repos / booking-data-exporter

booking-data-exporter

ASP.NET Core service that listens for booking finished/generated events and manual sync requests, exporting bookings to downstream systems (currently TTAND) with sync history in MongoDB.

100 · greenlowlooseOn-premZDD: no excuseapi

Health score

100

0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.

Runtime currency / 25

Runs on supported modern .NET

Legacy transport / 15

No legacy WCF or SOAP surface

Test posture / 15

Good test coverage

Security hygiene / 15

No credentials found in source

Dangerous coupling / 15

No dangerous coupling detected

Activity / 10

Actively maintained

Deployment hygiene / 5

CI in place

Health over time

No change since 2026-07-24 (100 to 100).

Facts

Languages	csharp
Frameworks	ASP.NET Core 8, TickerQ
Runtimes	.NET 8
Tests / CI	good / CI in place
Last commit	2026-06-18
Owner	Owner unknown (mapping to be curated)
Domain	Data and insight (system generated; curate in repo-owners.json to override)
Product area	Phenix
Hosted	On-prem Deployed to our own machines Release "booking-data-exporter": QA: deployment-group phase (agents on our own machines) Release "booking-data-exporter": Staging: deployment-group phase (agents on our own machines) Release "booking-data-exporter": Production: deployment-group phase (agents on our own machines) Release "booking-data-exporter": Training: deployment-group phase (agents on our own machines) build "booking-data-exporter" (build-booking-data-exporter.yml): on-prem signal "onPremiseDeploy: true" (runs on our own Docker hosts)
Releases	1 release pipeline(s): booking-data-exporter
Integration	rest, redis-streams
Source	Open in Azure DevOps

Risk flags

No risk flags recorded.

Each flag links to its glossary definition.

Dependencies in context

View in full graph

Laying out the graph…

greenamberreddata store (square, dashed link)Node size follows fan-in. Click any node to open it.

Entanglement

loose No binding mechanisms apply: this system needs no untangling work.

Depends on / used by

Depends on (1)

company-info-api

Used by (0)

No internal dependents.

Data stores

mongodb:BookingDataExporter redis:tickerq-job-store

Migration playbooks

Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.

ZDD adoption

No excuse

Nothing technical is holding this repo on the three-week release. It either already deploys without downtime (AWS) or is a modern, well-tested service the automated stealth path can carry today. Modern runtime, good tests, no hosted legacy transport: the automated stealth path can carry it today.

Dependencies and gotchas

Serialized state or messages in flight (Redis or queues): new code must deserialize objects written by the previous version

Steps

Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
Audit serialized data: anything in Redis, queues or shared caches must deserialize cleanly across adjacent versions.
Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.

SQL Server exit

Not applicable

No SQL Server dependency is recorded for this repo. Nothing to migrate.

Containerisation

Ready to containerise

Modern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).

Steps

Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
Log to stdout and expose a health check endpoint so ECS can supervise it.
Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.

Recommended actions

No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.

Assessment notes

booking-data-exporter

Purpose

Exports Travel Counsellors bookings to third-party downstream systems (currently the TTAND API). It accepts manual sync requests via HTTP and consumes BookingFinishedAndGenerated events from Redis Streams, queueing work through the TickerQ scheduler and orchestrating per-company sync mechanism selection.

Tech stack

C# on .NET 8 (Microsoft.NET.Sdk.Web), central package management (Directory.Packages.props), .slnx solution.
TickerQ for job scheduling/dashboard, Swashbuckle for Swagger, StyleCop rulesets enforced.
Internal TC platform libraries: TC.ConnectionBroker (Api/Redis/Mongo/Wcf/Aws), TC.Streams (+ Redis provider), TC.UserAccount.ServiceClient, TC.Phenix.CompanyInfo, TC.Phenix.Accounts.Events.

Deployment

Single build pipeline (booking-data-exporter) and single release pipeline (booking-data-exporter), release_count 1. CI YAML (build-booking-data-exporter.yml) uses shared azure-pipelines-templates, builds a Docker image (booking-data-exporter-api) on Linux agents with Traefik support and on-premise deploy.

Dependencies

Internal: consumes NuGet client packages for TC ConnectionBroker, Streams, UserAccount and Phenix CompanyInfo services; no source-level references to other estate repos confirmed.
External: TTAND booking API (export target), AWS S3 (AWSSDK.S3, planned parsed-booking archive).

Data stores

MongoDB database BookingDataExporter (BookingSyncRecords collection) for sync attempt history.
Redis used for TickerQ job storage/caching and as the event stream source.

Integration points

REST API (booking sync endpoints, Swagger UI, TickerQ dashboard).
Redis Streams consumer for booking events; WCF client capability present via TC.ConnectionBroker.Wcf.

Code health

Actively developed (last commit 2026-06-18). Dedicated tests/ tree with API flow/unit tests and parser tests. Modern SDK-style projects, nullable enabled, analyzers/StyleCop configured, ADRs and docs folders present.

Modernisation risks

Low risk: current .NET 8 runtime, containerised, tested, active. Main considerations are coupling to proprietary TC.ConnectionBroker/TC.Streams libraries and a hard dependency on the external TTAND API contract.