Shared services

Introduction

Shared services are workflow blocks that aren't visible in the diagram—they don't have a corresponding hexagon—, but are automatically included in asynchronous workflows when they are published in a runtime.

Like other blocks, they become pods in the Kubernetes cluster of the runtime where the workflow is published and therefore have a footprint in terms of CPU, memory, and ephemeral storage. Collectively, workflow's shared services constitute the so-called "asynchronous quota" of a workflow's resource requirements within the publication runtime.

All services have the same deployment properties, which are common to several other components and are described in the dedicated article.

Output Producer

The Output Producer service takes care of preparing the workflow output. This service is always present in any asynchronous workflow.

Script Interpreter

The Script Interpreter service supports the interpretation of scripts. It is present when the workflow contains at least one block of one of the following components:

• Python Interpreter
• JavaScript Interpreter v. 2.0.0
• Switch
• Map

Proxy Legacy

The Proxy Legacy service allows using old components that are not compatible with the latest implementation of asynchronous mode. It is present only if such components are used in the workflow.