MTS

Middle Tier Service

Overview

The Middle Tier Service (MTS) acts as the primary interface for preserving data state for the authoring environment. MTS is responsible for performing CRUD operations over a RESTful API, generating system and email notifications, and aiding in the orchestration of sync-all operations.

Service Mesh

Interactions

Workload performs the following interactions:

• Serves as the RESTful API for CAT-RCKMS, the primary user interface for RCKMS

• Utilizes the Authoring Database for storing data state for authoring and system activities

• Provides Jurisdiction, Concept, and Reporting Specification datasets to DSUS

• Performs session authentication for RRS

Placement

Workload should be deployed to the authoring environment.

Pod Specification

Attributes

Parameter	Value
Name	middle-tier-service
Restart Policy	Always
Termination Grace Period (seconds)	45
Tolerations (optional for AIMS environments)	N/A

Containers

MTS Container🚮GC Logging for Java

The Cloud SQL Proxy sidecar container notated below is only applicable for HLN's internal environments, and should not be deployed in AIMS environments.

🪢Cloud SQL Proxy

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	2
Minimum Ready Seconds	30
Maximum Surge	1
Maximum Unavailable	0

Non-Production Environments

Workload Identity

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