[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Choose Cloud Tasks or Pub/Sub\n\nBoth [Cloud Tasks](/tasks/docs/dual-overview) and\n[Pub/Sub](/pubsub/docs/overview) may be used to\nimplement message passing and asynchronous integration, but while they\nfunction in similar ways, they are not identical. This page helps you choose the\nright product for your use case.\n\nKey Differences\n---------------\n\nThe core difference between Pub/Sub and Cloud Tasks is the\nnotion of implicit vs explicit invocation.\n\nPub/Sub aims to decouple publishers of events and subscribers to those\nevents. Publishers do not need to know anything about their subscribers. As a result,\nPub/Sub gives publishers no control over the delivery of the messages save for\nthe guarantee of delivery. In this way, Pub/Sub supports **implicit** invocation:\na publisher implicitly causes the subscribers to execute by publishing an event.\n\nBy contrast, Cloud Tasks is aimed at **explicit** invocation where the publisher\nretains full control of execution. In particular, a publisher specifies an\nendpoint where each message is to be delivered.\n\nIn addition, Cloud Tasks provides tools for queue and\ntask management unavailable to Pub/Sub publishers, including:\n\n- Scheduling specific delivery times\n- Delivery rate controls\n- Configurable retries\n- Access and management of individual tasks in a queue\n- Task/message creation deduplication\n\nDetailed feature comparison\n---------------------------"]]
