Before you upgrade to the latest App Engine services SDK version, review the migration overview.
You can migrate to Cloud Tasks automatically by updating your
App Engine services SDK to the latest version. After you upgrade, the SDK
automatically redirects PushQueue calls to the Cloud Tasks
frontend APIs for you. Cloud Tasks retains your existing task
queues and tasks, so no additional migration is required.
Behind the scenes, the updated SDK uses the Cloud Tasks APIs to maintain feature parity with Task Queues features, the SDK supports the following:
- Batch task creation: The SDK uses batch APIs to support adding up to 100 tasks in a single call.
- Task-level retries: The SDK supports task-specific retry configurations.
Pricing and quotas
Migrating your push queues to Cloud Tasks might affect the pricing and quotas for your app.
Pricing
Review the Cloud Tasks pricing to estimate your monthly cost before migrating.
Similar to Task Queues, sending requests to your App Engine app with a Cloud Tasks push target is free. However, unlike Task Queues, Cloud Tasks charges for operations performed, such as creating, deleting, or managing tasks. This might lead to higher overall monthly cost compared to the complimentary App Engine Task Queue.
Quotas
Cloud Tasks requests also count towards your App Engine requests quotas.
Like Task Queues, Cloud Tasks has service-specific quotas. Migrating to Cloud Tasks will likely change your quotas.
Optimize request latency
Because the updated SDK sends requests directly to the Cloud Tasks API, enqueuing or deleting individual tasks sequentially can increase request latency compared to the legacy Task Queues service. To minimize latency:
- Batch multiple tasks into a single call: Group tasks into batch add calls (up to 100 tasks per call) instead of enqueuing tasks one by one in a loop.
Before you begin
Complete the following steps before migrating push queues to Cloud Tasks:
Make sure that you have access to the App Engine source code.
Enable the Cloud Tasks and Cloud Scheduler APIs:
To ensure that the App Engine service account has the necessary permissions to let the SDK dispatch tasks to the Cloud Tasks API, ask your administrator to grant the Cloud Tasks Enqueuer (
roles/cloudtasks.enqueuer) IAM role on the project.
Update the App Engine services SDK
Ensure your application uses the latest version of the App Engine services SDK.
In your
composer.jsonfile, updategoogle/appengine-php-sdkto version^2.3or higher and addgoogle/cloud-tasks.{ "require": { "google/appengine-php-sdk": "^2.3", "google/cloud-tasks": "^2.3" } }
Enable Cloud Tasks routing
runtime: php85 service: my-service-b env_variables: APPENGINE_USE_CLOUDTASK_PUSH_QUEUE: "true"Deploy your app:
gcloud app deployTo verify that your app is using Cloud Tasks, go to the Cloud Tasks page in the Google Cloud console.
What's next
- Cloud Tasks documentation
- Cloud Tasks client library
- Cloud Tasks REST reference overview
- Cloud Tasks RPC reference overview