Skip to main content

Mesh Node

The Mesh Node is the co-ordination layer for how the Transit Merchant Network operates within the merchant environment. It can be configured through a control console (web app) where services can be deployed to the network. It serves as both the Control Plane (for coordination of the Transit Desktop Agent fleet and deployed services) and the Data Plane (for executing transactions against deployed services).

On boot, the Transit Desktop Agents connect to the Mesh Node(s), allowing for precise control and centralised view of

  • fleet-wide configuration
  • request tracing and logging
  • health checks for Transit Desktop Agent and connected live network scanners
  • version enforcement and firmware distribution

The Mesh Node can also be self-hosted in the merchant's local data centre as illustrated below.

An example of the mesh node deployed in the merchant’s environment. Figure 1: An example of the mesh node deployed in the merchant’s environment.

Installation, Persistence & Security​

The Mesh Node is distributed as a docker container, executable or jar for execution within the merchant back office cluster with a number of deployment mechanics available. Transit solution engineers will tailor the Mesh Node distribution to merchant environments and requirements. The Mesh Node can be installed using kx Process Manager.

Transit Nodes can be backed by a number of different persistence modules to suit existing Merchant operational expertise and existing storage systems. Out of the box persistence options include H2, MySQL, Microsoft SQL Server, Oracle DB, PostgreSQL, SQLite, Kafka, LMDB, RocksDB, Xodus and more coming (speak to us about your requirements).

Mesh Node versions are signed and checksummed, with local validation performed each run. The Mesh Node performs version enforcement on all Transit Desktop Agents, ensuring the host is up-to-date and configured to the policy requirements of the merchant, with same-day security patches distributed fleet wide. All communication to the Transit API is end-to-end encrypted using TLS 1.3 and data policies are controllable and enforced by the mesh.