Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed
Repos / tc-redis-cache-event-viewer

tc-redis-cache-event-viewer

Angular 6 single-page app that connects to the redis cache event socket server over socket.io and displays a rolling list of the last 20 TC.Cache CacheEntryCreated events with their originating application and call stack.

61 · ambermediumlooseAWSZDD: not applicableweb-uidormant

Health score

61

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
4
End-of-life runtime outside .NET Framework
Legacy transport / 15
15
No legacy WCF or SOAP surface
Test posture / 15
8
Some tests, coverage is thin
Security hygiene / 15
15
No credentials found in source
Dangerous coupling / 15
15
No dangerous coupling detected
Activity / 10
0
Dormant: no meaningful change for two years or more while still deployed
Deployment hygiene / 5
5
CI in place
Health over time
2026-07-24 (run-2026-07-24-1): 612026-07-27 (run-2026-07-27-1): 61
No change since 2026-07-24 (61 to 61).

Facts

Languagestypescript
FrameworksAngular 6
RuntimesNode 8.12, nginx 1.13
Tests / CIsome / CI in place
Last commit2018-10-17
OwnerOwner unknown (mapping to be curated)
DomainPlatform services (system generated; curate in repo-owners.json to override)
Product areaShared platform
HostedAWS Deployed to AWS
  • build "redis-cache-event-viewer master": AWS task in designer pipeline
Releases1 release pipeline(s): redis-cache-event-viewer
Integrationwebsocket
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

loose No binding mechanisms apply: this system needs no untangling work.

    Depends on / used by

    Used by (0)
    No internal dependents.

    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

    Not applicable

    Not a deployed service (libraries, database definitions, desktop apps) or a retirement candidate not worth the investment. Retirement or consolidation candidate; do not invest in ZDD adoption.

    SQL Server exit

    Not applicable

    No SQL Server dependency is recorded for this repo. Nothing to migrate.

    Containerisation

    Retire instead

    This repo is a retirement or consolidation candidate; containerising it would be investment in something we intend to switch off.

    Recommended actions

    Review tc-redis-cache-event-viewer for retirement

    Dormant (last commit 2018-10-17) yet still release-linked, and nothing depends on it. Confirm remaining use, then retire and disarm its pipeline.

    Impact: Shrinks the estate before the expensive work begins

    proposed

    Assessment notes

    tc-redis-cache-event-viewer

    Purpose

    A diagnostic dashboard for the TC.Cache layer: a single Angular component subscribes to CacheEntryCreated events via SocketService and renders the latest 20 events (event name, cache name, application, call stack) so engineers can watch cache activity across the estate in real time.

    Tech stack

    Angular 6.1 with Angular CLI 6.2, TypeScript 2.9, RxJS 6, socket.io-client 2.1; Karma/Jasmine unit specs and a Protractor e2e scaffold. Built on Node 8.12 and served as static files from an nginx 1.13-alpine Docker image. Note ioredis is listed as a browser dependency but is unused — the app only talks to the socket server.

    Deployment

    prod_application with 1 release: release pipeline redis-cache-event-viewer from classic build pipeline redis-cache-event-viewer master (no pipeline YAML in the repo). The two-stage Dockerfile runs ng lint, ng test and ng build --prod at image build time, so lint and tests gate the build; a generate-compose-file.sh emits a compose file exposing the nginx container on port 8088.

    Dependencies

    Internal: entirely dependent on tc-redis-cache-event-socket-server for its data feed. External: none — no other APIs are called.

    Data stores

    None. All data arrives over the websocket; nothing is persisted.

    Integration points

    socket.io websocket client only. The socket server URL is hardcoded in socket.service.ts as http://dockerdev.travelcounsellors.com:8089 (a dev hostname) with no use of Angular environment files.

    Code health

    Only the CLI-generated "should be created" specs exist, so effective coverage is minimal despite tests running in the Docker build. README is the stock Angular CLI scaffold. Dormant since 2018-10-17, in lockstep with its socket server.

    Modernisation risks

    Angular 6 and Node 8 are both long end-of-life, and the toolchain (Protractor, TSLint, Karma) is entirely deprecated. The hardcoded dev socket URL means the production build points at a dev host, which questions whether the deployed instance works at all. As a two-file diagnostic tool it is a retire-or-rewrite candidate alongside tc-redis-cache-event-socket-server rather than an upgrade candidate.