What is a Workload?

In Synadia Cloud, workloads run on our globally deployed Nexus. In Synadia Platform, workloads run in your own infrastructure. Both allow you to focus on your application and not the infrastructure, with full management of scaling, placement, and health of your workloads.

How does it work?

From the UI, you can step through the process of creating a workload. You can specify the placement tags and the artifact. Once you have created the workload, the platform provides you with logs and metrics to monitor the health of your workload.

What is a Placement Tag?

Workloads support placement tags like NATS servers. Tags are defined on the Nex node and then workloads can be placed based on those tags.

In Synadia Cloud, these match the existing placement tags. For example, if you tag a workload cloud:aws, your workload will be placed in AWS. If you tag a workload cloud:gcp and geo:west, your workload will be placed in GCP's west region.

In Synadia Platform, placement tags can be defined as desired.

What is a Managed Workload Type?

Two types of workloads are currently supported: container and function. When you deploy a workload, it is sandboxed and isolated from other workloads. Interoperability between workloads is achieved through the use of NATS. container types will inject environmental variables with the NATS connection information. function types will have the NATS connection information available in the local context of the function.

What is a Workload Lifecycle?

Workloads have one of the following lifecycle states:

• service - The workload will restart automatically if it exits unexpectedly up to a max number of restarts defined in the configuration.
• function - The workload will be maintained in a "warm" state. In order to invoke the function, a NATS message must be sent to the function's trigger subject.