	In Browser
	StumbleUpon
	del.icio.us
	Google
	Google Buzz
	reddit
	LinkedIn

	Facebook
	Twitter
	Linkedin
	E-Mail

Cloud Platforms > Google Cloud Platform (GCP) > Cloud Tasks

Cloud Tasks

Author: Venkata Sudhakar

Google Cloud Tasks is a fully managed asynchronous task execution service. It allows you to separate out work that can be performed independently and dispatch that work asynchronously using worker services like Cloud Run or App Engine.

Key Features of Cloud Tasks:

1. Asynchronous execution - Offload work from your main application to background workers.

2. Guaranteed delivery - Tasks are persisted and retried automatically on failure.

3. Rate limiting - Control the rate at which tasks are dispatched to workers.

4. Scheduling - Schedule tasks to execute at a specific time in the future.

5. HTTP targets - Dispatch tasks to any HTTP endpoint including Cloud Run and external URLs.

The below example shows how to create and add a task to a Cloud Tasks queue using the Java client library.

import com.google.cloud.tasks.v2.CloudTasksClient;
import com.google.cloud.tasks.v2.HttpMethod;
import com.google.cloud.tasks.v2.HttpRequest;
import com.google.cloud.tasks.v2.QueueName;
import com.google.cloud.tasks.v2.Task;
import com.google.protobuf.ByteString;
import java.nio.charset.Charset;

public class CloudTasksExample {

public static void main(String[] args) throws Exception {
        String projectId = "your-project-id";
        String location = "us-central1";
        String queueId = "my-task-queue";
        String workerUrl = "https://my-worker-service.run.app/process";

try (CloudTasksClient client = CloudTasksClient.create()) {
            QueueName parent = QueueName.of(projectId, location, queueId);

// Build the task payload
            String payload = "{"userId": "user-123", "action": "send-email"}";

// Create an HTTP task
            Task task = Task.newBuilder()
                .setHttpRequest(
                    HttpRequest.newBuilder()
                        .setUrl(workerUrl)
                        .setHttpMethod(HttpMethod.POST)
                        .putHeaders("Content-Type", "application/json")
                        .setBody(ByteString.copyFrom(payload, Charset.defaultCharset()))
                        .build())
                .build();

// Add the task to the queue
            Task createdTask = client.createTask(parent, task);
            System.out.println("Task created: " + createdTask.getName());
            System.out.println("Task state: " + createdTask.getDispatchCount());
        }
    }
}

It gives the following output,

Task created: projects/your-project-id/locations/us-central1/queues/my-task-queue/tasks/1234567890
Task state: 0

Cloud Tasks vs Cloud Pub/Sub:

Cloud Tasks - Use when you need explicit task management, deduplication, scheduling, rate limiting, and individual task tracking. Best for job queues where each task has a specific worker.

Cloud Pub/Sub - Use when you need fan-out messaging to multiple subscribers, high-throughput event streaming, and decoupled publish/subscribe architectures.

Send your comments, suggestions or queries regarding this site to [email protected].