cron- invoke process on schedule
deploy- invoke process when Lair is deployed; used to start long-running processes such as active services
http- invoke process when a request is made to a HTTP endpoint
.triggersfile stored within your Lair’s root directory. Open the
.triggersfile from your file system and select “+ New Trigger” to add a new trigger.
.triggersfile. You will also have to “Push” your workspace’s file system to update this configuration on your remote Lair.
.triggersfile, select an existing trigger to open the configuration modal. Press “Run” to execute your trigger’s run command and start the process execution. See Processes for more details on how to view and manage processes.
httptrigger routes HTTP requests to independent, asynchronous processes running in separate containers, while using the
deploytrigger routes HTTP requests to a running service process in a single container.
httptriggers vs. running service processes deployed via the
deploytrigger will ALWAYS have higher latency due to serverless execution. When a request is made to an
httptrigger, the WayScript system must provision a new container, install any new dependencies, and attach logs before the request can be returned.
httptriggers to your Lair and specify different paths for each trigger, but setting up a running service process gives you unlimited scalability of endpoints and more fine-tuned control of endpoint characteristics.
httptriggers will be torn down on process exit, and therefore in cases of low volume of requests, this approach will use less system runtime.