Stack 9 Azure Cloud

This guide shows you how to initialize a TAFJ/Transact environment deployed in containers and to configure the relevant networking elements to facilitate message flow. This is independent of the database in use or the release of Transact/TAFJ present in the deployment.

Overview

Transact is a modern, API driven, application. The business logic is hosted in a private AKS cluster, which is inaccessible from outside of the virtual network. Public access to the elements in the vNet is exposed via a public IP Address associated with an Application Gateway instance. Message flow from the application gateway to the container is handled via an Application Gateway Ingress Controller (AGIC).

The primary difference between on-premise and cloud-native architecture is that on-premise Transact and third party software are installed and run on physical and virtual hardware managed by the clients. With the Azure cloud native reference architecture they run in containers in public Azure cloud. This allows for handling of the maintenance of these machines to Microsoft Azure and not the clients.

This is a tested and proven reference architecture. Our customers and prospects should treat this as a model and are free to change any part of this according to their preferences.