backoffice-balanceduedate-api
API that calculates the balance due date for a booking component, or the earliest due date across multiple components or a whole booking.
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 |
| Runtimes | .NET 8 |
| Tests / CI | good / CI in place |
| Last commit | 2026-04-21 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Payments and finance (system generated; curate in repo-owners.json to override) |
| Product area | Phenix |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 2 release pipeline(s): \finance\backoffice\backoffice-balanceduedate-api CI; \finance\backoffice\backoffice-balanceduedate-api Stealth |
| Integration | rest, wcf |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Speaks WCF (client)
Detaches when its WCF surface gains a modern interface or its WCF calls move to one.
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
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. Modern runtime, good tests, no hosted legacy transport: the automated stealth path can carry it today. Calls legacy WCF endpoints as a client; stay dual-version safe on client package upgrades.
- 1 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
- Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
- 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 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
backoffice-balanceduedate-api
Purpose
Extracts balance-due-date logic out of the legacy BackOffice service into a standalone REST API. Callers pass component details and/or a Booking ID; when a Booking ID is supplied the API loads that booking's components via the Phenix booking service and returns the earliest balance due date. Consumers include the Quote System and (planned) BackOffice Accounts Service.
Tech stack
Single ASP.NET Core project on .NET 8 with Asp.Versioning, Swashbuckle 9, PhenixAuth authentication, Scrutor, TC.ConnectionBroker (Api, Mongo, Wcf, HttpClient), TC.Phenix.Services.Client, WebApi.Logger, TC health-check extensions. Rule-based date calculation engine in Services.
Deployment
2 release pipelines under \finance\backoffice\ (backoffice-balanceduedate-api CI and a Stealth variant) fed by the backoffice-balanceduedate-api CI build. CI uses shared InternalOSS/azure-pipelines-templates with a weekly scheduled Friday build. Per-environment appsettings for QA, Training, PreProduction, Live, DataFixQA, LiveProviderQA.
Dependencies
- Internal: outbound WCF call to the Phenix Booking service (
BookingServiceFacadeServiceClientoverIWcfConnectionBroker) to load booking components; shared TC NuGet libraries (ConnectionBroker, Phenix.Services.Client, PhenixAuth). No estate repo mapped with confidence. - External: New Relic APM only.
Data stores
MongoDB balanceduedateapi_logs for request/response logging via WebApi.Logger. No SQL database owned by this service; booking data is fetched via the booking service.
Integration points
Inbound versioned REST API with Swagger. Outbound WCF SOAP to the legacy Phenix booking service via TC.ConnectionBroker.Wcf.
Code health
Good: a SpecFlow-style BDD test project (Features/Drivers) plus a unit-test project, CI templates, weekly scheduled build, and a design document (Balance Due Date Service v1.4.pdf) in the repo. Last commit 2026-04-21.
Modernisation risks
Low. Modern .NET 8 stateless service; main residual risk is the outbound dependency on the legacy WCF booking service, which ties it to the Phenix SOAP estate.