tc-streams-masstransit-adapter
.NET 8 adapter service that consumes BookingChanged events from TC Streams (Redis Streams), enriches them with contact and backoffice accounts data, and republishes them as MassTransit messages on Amazon SQS.
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, MassTransit 8.5, MediatR, Mapster |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2026-04-01 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Platform services (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-streams-masstransit-adapter |
| Integration | redis-streams, masstransit, graphql, rest, 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
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.
- 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.
- 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-streams-masstransit-adapter
Purpose
A bridge between the estate's two messaging worlds: it subscribes to BookingChangedEvent (from the TC.Phenix.Accounts.Events contract) on the internal TC Streams Redis-stream bus, enriches each event with customer contact details from the contact API and booking/invoice detail from the backoffice Accounts GraphQL API, then publishes the enriched event to MassTransit over Amazon SQS for consumers outside the streams ecosystem (CX systems).
Tech stack
C# on .NET 8 (Generic Host console app, nullable enabled). TC.Streams 8.1 with the Redis provider and MediatR-based IReceivedEventHandler integration; MassTransit 8.5 with AmazonSQS transport and TC endpoint-name formatters; GraphQL.Client 6, Mapster, Polly, FluentResults; TC.ConnectionBroker 1.20 (Redis/Api/Aws) for all connection and credential resolution. Nerdbank.GitVersioning and the full analyser set (Sonar, NetAnalyzers, SecurityCodeScan) via Directory.Build.props.
Deployment
prod_application with 1 release: release pipeline \cx\tc-streams-masstransit-adapter from the in-repo YAML build-streams-masstransit-adapter.yml (shared azure-pipelines-templates CI job, dotnet SDK 8.x, Linux agents). Ships as Docker image aws-streams-masstransit-adapter with an on-premise container deploy.
Dependencies
Internal: TC.ConnectionBroker.* (tc-connectionbroker); TC.Phenix.Accounts.Events event contracts and the Accounts GraphQL API (backoffice); contact API client calling phenix-contact-api; plus TC.Streams / TC.MassTransit.AmazonSQS / TC.CostSavings.Domain framework packages with no included-repo mapping. External: Amazon SQS (eu-west-1), with AWS credentials fetched at runtime from the connection broker (CX_TcStreamsMasstransitAdapterUser) — no secrets in source.
Data stores
None owned. Reads the shared TC Streams Redis instance (connection-broker target Streams) as its event source.
Integration points
Redis Streams inbound; outbound GraphQL to backoffice accounts, REST to the contact API, and MassTransit publish over SQS.
Code health
One xunit unit-test project covering the BookingChangedEventHandler and its enrichment logic (NSubstitute, FluentAssertions, coverlet) — focused but narrow. YAML CI with analysers enforced. Recently maintained (last commit 2026-04-01). README is untouched boilerplate.
Modernisation risks
Low: modern .NET 8, containerised, YAML CI, no secrets in source. It is glue code whose lifetime is tied to the Redis-Streams-to-SQS split — if the estate consolidates on one bus the adapter disappears. Enrichment makes two synchronous calls per event, so it inherits availability risk from backoffice GraphQL and the contact API.