You can create HTTP tasks using either the
(Preview) or the
CreateTask method. This
page provides guidance on how to choose between the two methods for creating
BufferTask method (Preview) lets you
create a task by sending an HTTP request to the queue. The
lets you create a task by constructing the task object. For most use cases,
explicitly constructing the task object is unnecessary. The best method for
creating tasks depends on whether your queue has queue-level routing.
Check if your queue has queue-level routing
Run the following gcloud CLI command in your terminal:
gcloud beta tasks queues describe QUEUE_NAME
QUEUE_NAMEwith the name of your queue.
In the output, look for the field
httpTargetand check if the
uriOverridehas been set.
If the output includes a line for
hostspecified, your queue has queue-level routing. To choose your task creation method, see the section Queues with queue-level routing.
If the output does not include a line for
uriOverrideor if the
uriOverridedescription does not show a
hostspecified, your queue does not have queue-level routing. To choose your task creation method, see the section Queues without queue-level routing (or configure queue-level routing).
Queues with queue-level routing
For queues with queue-level routing, the task creation method depends on the task's routing requirements:
- Task has the same routing requirements as specified at the queue level:
BufferTask(Preview). Learn how to create tasks with the
- Task has different routing requirements from those specified at the queue-level:
Set the queue's
IF_NOT_EXISTSto ensure that the queue-level routing applies to tasks for which routing does not exist (for example,
BufferTasktasks), but respects the routing of tasks that carry their own routing specifications. Then use
CreateTask. This method lets you specify individual routing for the task. Learn how to create tasks with the
Queues without queue-level routing
For queues without queue-level routing, create tasks by using the
queue-level routing). The
CreateTask method includes specifying routing for
the task, which is required for queues that don't already have routing
information at the queue-level. Learn how to create tasks with the
Understand queue-level routing
Queue-level routing lets you specify default routing information for tasks based on the queue they're in. You can specify whether you want the default routing to apply only to tasks that don't have their own routing information, or to all tasks.
Choose queue-level routing if you want to:
- Create tasks with standard HTTP requests (rather than by constructing the task object)
- Use a queue as a buffer in front of a target service
The per-target approach
Queue-level routing works best with architectures that use one queue for each target service. This model lets you:
- Manage tasks based on their target (for example, redirecting a group of tasks if the target service is down)
- Send all tasks in a queue to the same target
- Create tasks without explicitly constructing the task object (by using the
BufferTaskmethod that is in Preview)
Turning queue-level override behavior on and off
Once you configure queue-level routing, you can decide when it gets enforced by setting the queue's UriOverrideEnforceMode.
IF_NOT_EXISTS: The queue-level routing applies only when a task doesn't contain its own routing information. Use this setting if you want the queue to be able to dispatch tasks to different targets.
ALWAYS: The queue-level routing always applies, even if a task contains its own routing information. Any routing information set at the task level is overridden by the queue-level routing. Use this setting if you want to require tasks in a given queue to use the same routing information.