What is a Workload?

Synadia Cloud will manage the lifecycle of your compute for you on our globally deployed Nexus. This allows you to focus on your application and not the infrastructure. We will manage the 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, Synadia Cloud provide you with logs and metrics to monitor the health of your workload.

What is a Placement Tag?

Workloads use the same placement tags as JetStream resources. If you tag a workload cloud:aws, Synadia Cloud will ensure your workload is placed in AWS. If you tag a workload cloud:gcp and geo:west, Synadia Cloud will ensure your workload is placed in GCP's west region.

What is a Managed Workload Type?

Synadia Cloud supports deploying 2 types of workloads: container and javascript. 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. javascript types will have the NATS connection information available in the global nats object.

What is a Workload Lifecycle?

Nex workloads have one of the following lifecycle states:

• service: Nex will restart the workload if it exits unexpectedly up to a max number of restarts.
• job: Nex will not try to restart the container after any exit.
• function: Nex will maintain the workload in a "warm" state. In order to invoke the function, a NATS message must be sent to the function's trigger subject.

Type Summary