SSCS

Shared Service Comparison Service

Overview

The purpose of this service is to receive and store output from 2 different versions of the Shared Service and then compare that output and report any differences.

The individual Shared Service outputs are submitted to this service separately and then "paired" by a unique identifier, called a comparison set key.

Processing (comparing) is done asynchronously from the call to submit the output. REST endpoints are available for retrieving details about comparisons performed, e.g. differences detected and stats.

Flow Diagram for SSCS Workload

Service Mesh

Interactions

Workload requires connectivity to the Document store database for storing comparison records.

Placement

Workload should be deployed to the reportability environment.

Pod Specification

Attributes

Parameter	Value
Name	ss-comparison-service
Restart Policy	Always
Termination Grace Period (seconds)	30
Tolerations (optional for AIMS environments)	N/A

Containers

SSCS Container🚮GC Logging for Java

Volumes

This pod requires one volume:

• A volume named java-diag, of type empty_dir with the medium parameter left blank or set to an empty string (""). This is used by the Java GC Logging common sidecar container.

Workload Definition

Production Environments

Provision workload as a Kubernetes Deployment resource, with RollingUpdate strategy and the following attributes for nominal operation state:

Parameter	Value
Replicas	1
Minimum Ready Seconds	10
Maximum Surge	1
Maximum Unavailable	0

Non-Production Environments

Workload Identity

A Kubernetes Service Account named ss-comparison-service should be associated with this workload, for bindings specified in containers.