Terminology<\/h3>\n\n\n\nLet’s get a few basic terms out of the way before we jump into setting this up. Since some of these are quite similar and easy to confuse (particularly job and task) we thought we better make them clear.<\/p>\n\n\n\n
Queue Module<\/h4>\n\n\n\n
The queue module provides access to a specific type of queue platform (e.g., Amazon SQS). You’ll configure a particular queue module depending on what service you’re using. Right now we’ll just cover SQS.<\/p>\n\n\n\n
Queue<\/h4>\n\n\n\n
A queue is the place where jobs are stored. The queue manages the life cycle of a job (see below). The queue is externally hosted and not part of RealityServer.<\/p>\n\n\n\n
Command<\/h4>\n\n\n\n
The RealityServer command that will be called by a job to perform the actual work required. Jobs call a single command and this is just a regular RealityServer command (e.g., a custom V8 command you have written).<\/p>\n\n\n\n
Parameters<\/h4>\n\n\n\n
When calling a command in a job you usually will want to pass in parameters to the command, just like when calling a command directly. The parameters are included in the job and also stored in the queue.<\/p>\n\n\n\n
Task<\/h4>\n\n\n\n
The action you want to be performed after a queued job completes. This might be something like uploading an image rendered by the job to a server.<\/p>\n\n\n\n
Job<\/h4>\n\n\n\n
A job is a combination of a command, parameters and tasks. The job is what is inserted into the queue and what gets pulled off the queue when work is to be done.<\/p>\n\n\n\n