Open Beta

Glossary

This is a glossary of terms for Axway AMPLIFY Choreography.

A

AMPLIFY Choreography CLI Amplify Choreography Engine configuration and management command-line tool
Apache Kafka Open-source stream-processing software platform that is the messaging backbone for managing operational data
AWS Amazon Web services. Cloud computing services

B

business service Services and functions that make up a business flow

C

choreography Allows the publishing service to execute the service and publish the output without having to be aware of the subscribing services. This is a set of rules that determines which services will be executed, and in what order
container An executable image that contains software and its dependencies

E

executor Service that initiates the choreography

H

Helm Tool for managing Kubernetes charts. Charts are packages of pre-configured Kubernetes resources

I

Ingress controller NGINX third-party software that provides load balancing and traffic routing

J

Jaeger Based on the OpenTracing specification, which is comprised of the API specification, frameworks and libraries. It allows developers to add instrumentation to their applications

K

Kubernetes Open source platform used for managing containerized applications
Kubernetes cluster A set of machines (nodes) that run containerized applications. A cluster consists of at least one master node and several worker nodes

L

linkage Facilitates the execution of the business service for the payload received from the sidecar

P

payload Transmitted content that is the actual data and not a reference to the data
pod A set of running containers in a cluster

R

Runtime Service Infrastructure that runs your applications and pre-built services

S

secret name Kubernetes object used to store sensitive data such as user name and passwords with encryption
service An API object that describes how to access applications
sidecar Authenticates the service with the platform and registers it as a usable choreography step
span The primary building block of a distributed trace that represents a logical unit of work with some properties (for example: operation name, start time and the duration). Spans can be nested and ordered to model relationships
span context Trace information that accompanies the distributed transaction when it passes across process boundaries
step A single function applied to the data in a job flow

T

tenant A user or a workload
tenant ID A string that uniquely identifies the tenant
trace A data / execution path through the system. Also known as a directed acyclic graph of spans

 

Related Links