Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed
Repos / phenix-components-api

phenix-components-api

ASP.NET Core API supplying data (address lookup, user info, navigation links, date-picker config) to shared Phenix front-end components.

87 · greenlowkernelOn-premZDD: no excuseapi

Health score

87

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
25
Runs on supported modern .NET
Legacy transport / 15
6
Calls at least one legacy WCF endpoint
Test posture / 15
15
Good test coverage
Security hygiene / 15
15
No credentials found in source
Dangerous coupling / 15
11
depends on pinning component(s): phenix-feature-service
Activity / 10
10
Actively maintained
Deployment hygiene / 5
5
CI in place
Health over time
2026-07-24 (run-2026-07-24-1): 872026-07-27 (run-2026-07-27-1): 87
No change since 2026-07-24 (87 to 87).

Facts

Languagescsharp
FrameworksASP.NET Core 8
Runtimes.NET 8
Tests / CIgood / CI in place
Last commit2026-07-22
OwnerOwner unknown (mapping to be curated)
DomainPlatform services (system generated; curate in repo-owners.json to override)
Product areaPhenix
HostedOn-prem Deployed to our own machines
  • Release "\flights-stream\phenix-components-api": QA: deployment-group phase (agents on our own machines)
  • Release "\flights-stream\phenix-components-api": Staging: deployment-group phase (agents on our own machines)
  • Release "\flights-stream\phenix-components-api": Production: deployment-group phase (agents on our own machines)
  • Release "\flights-stream\phenix-components-api": Training: deployment-group phase (agents on our own machines)
  • Release "\flights-stream\phenix-components-api": DR: deployment-group phase (agents on our own machines)
Releases2 release pipeline(s): \flights-stream\phenix-components-api; \flights-stream\phenix-components-api stealth
Integrationrest, wcf
SourceOpen in Azure DevOps

Risk flags

Each flag links to its glossary definition.

Dependencies in context

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

Entanglement

kernel Bound into the core by 2 mechanism(s).

Detaches when its pinning dependencies are cut or multi-targeted (phenix-feature-service); and when its WCF surface gains a modern interface or its WCF calls move to one.

Depends on / used by

Used by (1)
phenix-ui
Data stores
redis:shared-cache

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. Calls legacy WCF endpoints as a client; stay dual-version safe on client package upgrades.

Dependencies and gotchas
  • 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
  • Feature flags come from phenix-feature-service (WCF-only): flag reads themselves are a legacy dependency to watch
Steps
  1. Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
  2. 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.
  3. Audit serialized data: anything in Redis, queues or shared caches must deserialize cleanly across adjacent versions.
  4. Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
  5. 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).
  6. 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
  1. Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
  2. Log to stdout and expose a health check endpoint so ECS can supervise it.
  3. 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.
  4. 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

phenix-components-api

Purpose

Backend API that feeds shared Phenix UI components: address lookup, date picker configuration, navigation menus (links to intranet, insight reports, AnnounceKit widgets, Freshdesk support widget), and user details. One deployable web project (TC.Phenix.Components.API) fronting per-component class libraries.

Tech stack

C# on .NET 8, ASP.NET Core with Asp.Versioning API versioning and Swashbuckle/Swagger. PhenixAuth JWT authentication. Caching via TC.Cache with Redis storage. Modern SDK-style projects with Directory.Build.props and Nerdbank-style version.json.

Deployment

Included as prod_application with 2 releases. Single build pipeline phenix-components-api defined in azure-pipelines.yml using shared templates from InternalOSS/azure-pipelines-templates; builds on master and release/* branches. Release pipelines under \flights-stream\: phenix-components-api and a separate stealth pipeline.

Dependencies

Internal NuGet packages map to estate repos: TC.ConnectionBroker.* (tc-connectionbroker), TC.Exceptions.* (tc-exceptions), TC.UserAccount.ServiceClient (backoffice-useraccount-service), a WCF connected service for address lookup (backoffice-address-lookup-service), TC.DestinationManagement.API.Client (phenix-destination-management), TC.Phenix.CompanyInfo (company-info-api), and TC.Phenix.Feature (phenix-feature-service). Third-party: AnnounceKit widgets, Freshdesk support widget, SharePoint/insight URLs surfaced through navigation config.

Data stores

No direct database of its own; uses shared Redis cache (CacheStorage: redis) and reaches SQL/WCF back ends indirectly through TC.ConnectionBroker packages.

Integration points

REST (ASP.NET Core controllers, versioned, Swagger-documented). Outbound WCF calls (System.ServiceModel 6/8 packages, address lookup connected service) and REST clients via ConnectionBroker HttpClient extensions.

Code health

Good: six test projects mirroring the source components, plus an integration-style ApiTests project. YAML CI with shared templates. Actively maintained — last commit 2026-07-22, dependencies current (.NET 8, Extensions 10.x packages).

Modernisation risks

Low risk overall. Residual WCF client usage (address lookup and ConnectionBroker.Wcf) ties it to legacy WCF services elsewhere in the estate. A Freshdesk widget secret is committed in appsettings.json (sandbox, but a hygiene concern). Coupled to shared Redis cache and Phenix-wide auth libraries.