tc-public-travelcounsellors
.NET 8 API and MassTransit/SQS consumer that maintains and serves public Travel Counsellor profiles (bio, social media, travel types) from a PublicTravelCounsellors MongoDB store for the public website.
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 | ASP.NET Core 8, MediatR 12, MassTransit 8, FluentValidation 11, Mapster |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2025-08-27 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Public web (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | AWS Deployed to AWS
|
| Releases | 0 release pipeline(s): |
| Integration | rest, masstransit, sqs |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loose No binding mechanisms apply: this system needs no untangling work.
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 excuseNothing 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. Already deploys as a container to AWS, which releases without downtime today. Separating it from the three-week release is a process decision, not a technical one.
- 3 system(s) depend on this repo; during a rolling deploy they will talk to old and new versions at once, so responses must stay compatible
- Serialized state or messages in flight (Redis or queues): new code must deserialize objects written by the previous version
- 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.
- 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.
- Use ECS rolling deployments with health checks gating traffic, and take this service off the three-week release train.
- 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
Already containerisedIts pipelines already build containers and deploy to AWS. Nothing to do here.
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-public-travelcounsellors
Purpose
Read store and API for Travel Counsellor profile pages on the public website. Profiles arrive two ways: a MassTransit consumer receives CreateOrUpdateTravelCounsellorCommand messages over Amazon SQS (published twice daily by tc-travelcounellors-sync-service, which references this repo's TC.Public.TravelCounsellors.Contracts NuGet package), and an HTTP PUT api/travel-counsellors/{id} accepts the same command directly; GET api/travel-counsellors/{id} serves the profile. Handlers run through MediatR with FluentResults results and upsert into MongoDB.
Tech stack
C# on .NET 8 across five projects (Abstractions, Api, Contracts, domain, Persistence) in a .sln with Directory.Build.props, rulesets and Nerdbank-style version.json. MediatR 12, MassTransit 8.3 with TC.MassTransit.AmazonSQS extensions (TC endpoint-name formatters, exponential retry to 60 minutes), Mapster, FluentValidation 11, FluentResults, MongoDB.Driver via the Mongo connection broker, Swashbuckle, TC.Diagnostics health checks.
Deployment
Included as prod_application with 0 releases — YAML/AWS only. Build pipeline tc-public-travelcounsellors from azure-pipeline.yaml on the shared InternalOSS/azure-pipelines-templates jobs/ci.yml (SDK 8.x): packs the Contracts NuGet package and containerises the API into cx-public, deploying to ECS via the aws-public-tc-apps Terraform repo with tfvars, eu-west-1, functional area public.
Dependencies
Internal: TC.ConnectionBroker.* (tc-connectionbroker), TC.Diagnostics.HealthChecks (tc-diagnostics-portal); TC.MassTransit.AmazonSQS maps to no included repo. It is the upstream contract owner for tc-travelcounellors-sync-service rather than a dependent of it. External: Amazon SQS (eu-west-1) as the MassTransit transport.
Data stores
Owns the PublicTravelCounsellors MongoDB database (single TravelCounsellors collection), resolved through connection-broker target PublicTravelCounsellors.
Integration points
Inbound REST (Swagger always on; no authentication middleware is registered, so the PUT upsert endpoint appears anonymous) and inbound MassTransit consumption over SQS. No outbound service calls.
Code health
Some tests: three test projects but only ~16 facts/theories (consumer, handlers, exception middleware); the controller is ExcludeFromCodeCoverage. No README. Last commit 2025-08-27 — a stable, small, done-ish service.
Modernisation risks
Low. Current .NET 8, MassTransit and container deployment. The only real concerns are the apparently unauthenticated HTTP upsert path duplicating the bus route (an internet-exposed write if the ECS service is publicly routable), and the absent README for a repo that owns a cross-repo message contract.