Pub/Sub is an asynchronous and scalable messaging service that decouples services that produce messages from services that process those messages. Pub/Sub allows services to communicate asynchronously, often to stream analytics and empower data integration pipelines to ingest and distribute data. This page describes the differences between the Trusted Cloud and Google Cloud versions of Pub/Sub.
For more detailed information about Pub/Sub, see the Pub/Sub overview and the rest of the Pub/Sub documentation.
Key differences
There are some differences between the Trusted Cloud version of Pub/Sub and the Google Cloud version. Some notable differences include the following:
- Some types of subscriptions are unavailable in Trusted Cloud.
- Some types of import topics are unavailable in Trusted Cloud.
- Pub/Sub Lite is unavailable in Trusted Cloud.
- Some features, like ordering keys or dead-letter queues are unavailable in Trusted Cloud.
A more detailed list of differences is provided in the rest of this section. If you are already familiar with Google Cloud, we recommend that you review these differences carefully, particularly before designing an application to run on Trusted Cloud. We also recommend reviewing the general differences between Trusted Cloud and Google Cloud.
If you would like to use a particular Pub/Sub feature that isn't currently available in Trusted Cloud, contact Trusted Cloud support. To be notified when new features roll out in Trusted Cloud, subscribe to the release notes.
Features
| Authentication for push subscriptions | Authentication for push subscriptions is unavailable. |
| Dead-letter queues | Dead-letter queues are unavailable. |
| Exactly-once delivery | Exactly-once delivery is unavailable. |
| Filtering | Filtering is unavailable. |
| Import topics | Import topics are not available for use. Including Amazon Kinesis Data Streams import topics, Cloud Storage import topics, Azure Event Hubs import topics, MSK import topics, and Confluent Cloud import topics. |
| Ordering keys | Ordering keys are unavailable. |
| Payload unwrapping for push subscriptions | Payload unwrapping for push subscriptions is unavailable. |
| Schemas | Schemas are unavailable. |
| Snapshots and seek | Snapshots and seek are unavailable. |
| Subscriptions | BigQuery subscriptions and Cloud Storage subscriptions are unavailable. Ingesting data from sources like Amazon Web Services (AWS) or Cloud Storage is also unavailable. |
Availability and disaster recovery
| Regions and zones | Trusted Cloud is only supported in a single region and can be used in both regional and zonal configuration deployments. Zone separation in a single region is supported. Multi-regional functionality and features that rely on multi-regions are not supported. |
| Disaster recovery | Cross-region failover is unavailable for customers operating in universes with a single region. Zone separation within a region is supported. |
Architecture
| Global availability of data | Data in Trusted Cloud is not globally available. It is only available in a single region, specific to your universe. |
| Resource location and IAM controls | Resource location restrictions are not supported. |
Integrations
| Core integrations | The following core integrations aren't supported in Trusted Cloud: Dataflow, BigQuery subscriptions, Cloud Functions, App Engine, and Cloud Run. | Third party integrations | Third-party integrations might not be supported. To determine if a third-party integration is supported in Trusted Cloud, check with the respective vendor you are working with. |
Related guides
The following information might also affect how you use and design for Pub/Sub in Trusted Cloud by S3NS. These guides include general information about working in Trusted Cloud, including documentation, security and access control, billing, tooling, and service usage.
For details about other services and features in Trusted Cloud and their differences from their Google Cloud counterparts, see the product list.