tc-travelcounellors-sync-service
.NET 8 Quartz-scheduled service that twice daily merges Travel Counsellor profiles from the contact API and web-details API and publishes CreateOrUpdateTravelCounsellor commands to MassTransit over Amazon SQS for public-website consumers.
Health score
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.
Facts
| Languages | csharp |
| Frameworks | .NET Generic Host, Quartz 3.13, MassTransit, Mapster |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2026-01-26 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Identity and access (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 1 release pipeline(s): \cx\tc-travelcounsellors-sync-service |
| Integration | rest, masstransit, sqs |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Pinning dependency: phenix-feature-service
Detaches when its pinning dependencies are cut or multi-targeted (phenix-feature-service).
Depends on / used by
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
Ready with guardrailsClose: the deployment path exists, but specific checks are needed first, typically raising tests, auditing serialized data, or respecting a shared schema with expand and contract. Test coverage is thin; ZDD shifts the safety net onto automation.
- Serialized state or messages in flight (Redis or queues): new code must deserialize objects written by the previous version
- Feature flags come from phenix-feature-service (WCF-only): flag reads themselves are a legacy dependency to watch
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
- 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.
- 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 applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- 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
tc-travelcounellors-sync-service
Purpose
Keeps public Travel Counsellor profile data in sync: RefreshTravelCounsellorsJob runs on a Quartz cron (00:00 and 12:00 daily), fetches active Travel Counsellors from the contact API and per-company profile/social-media detail from the web-details API (companies filtered via company-info and feature flags), merges the two, builds social-media links, and publishes CreateOrUpdateTravelCounsellor commands (from TC.Public.TravelCounsellors.Contracts) onto MassTransit/SQS. Note the repo name itself carries a typo ("travelcounellors"); the release pipeline is spelled correctly (\cx\tc-travelcounsellors-sync-service).
Tech stack
C# on .NET 8 (Generic Host console app, three net8.0 projects). Quartz.Extensions.Hosting for scheduling, MassTransit + TC.MassTransit.AmazonSQS for publishing, Mapster, Polly, FluentResults, System.Linq.Async; TC.ConnectionBroker 1.20 (Api/Aws) resolves API endpoints and AWS credentials. Full analyser set (NetAnalyzers 9, Sonar 10, SecurityCodeScan) via Directory.Build.props.
Deployment
prod_application with 1 release: release pipeline \cx\tc-travelcounsellors-sync-service from the in-repo YAML build-sync-service.yml (shared azure-pipelines-templates CI). Ships as a Docker container (Dockerfile + entrypoint.sh, compose files for local use).
Dependencies
Internal: TC.ConnectionBroker.* (tc-connectionbroker); REST clients to phenix-contact-api and tc-web-details-api; TC.Phenix.CompanyInfo (company-info-api) and TC.Phenix.Feature (phenix-feature-service) for company/feature lookups; TC.Public.TravelCounsellors.Contracts message contracts (public-websites domain, no confirmed included-repo mapping). External: Amazon SQS (eu-west-1), credentials fetched at runtime from the connection broker (Public_TcTravelcounsellorSyncServiceMasstransitUser) — no secrets in source.
Data stores
None owned — it is stateless, reading from APIs and writing to the message bus.
Integration points
Outbound REST to the contact and web-details APIs; MassTransit publish over SQS. No inbound surface.
Code health
One xunit unit-test project covering the job, command mapper and social-media-link builder with coverlet — reasonable for its size. YAML CI, analysers enforced, recently maintained (last commit 2026-01-26). README is untouched boilerplate.
Modernisation risks
Low: modern .NET 8, containerised, YAML CI, tests present. Risks are operational rather than technical — a full-refresh batch design (every run re-publishes all counsellors) and synchronous dependence on two upstream APIs; the repo-name typo is a minor but permanent papercut in tooling and search.