Google Pub/Sub Agent for Gluesync: Target Integration
Core principles
Gluesync offers support for streaming data through Google Pub/Sub to let you focus on the development of your modern application stack and leave all the complexity of handling data sourcing from relational, NoSQL databases and data lakes to it.
Data could be modeled accordingly to your needs using Gluesync’s data modeling features and then sent immediately to a designated Kafka topic where it has written permissions to stream changes.
Communication between this agent and Google Pub/Sub is achieved through Google Pub/Sub’s Java SDK.
Platform supported features
| Feature | Support | Notes |
|---|---|---|
Target role |
✅ |
Publishes messages to Google Pub/Sub topics via the official Java SDK. |
Source role |
❌ |
Connector is target-only; Pub/Sub subscriptions are not ingested. |
Snapshots |
❌ |
Not supported, as this agent does not supporting reading from Pub/Sub. |
CDC |
❌ |
This agent does not currently support reading incremental changes from Google Pub/Sub. |
CDC type |
N/A |
This agent does not currently support reading incremental changes from Google Pub/Sub. |
Bulk load |
N/A |
Publishing already batches messages efficiently; no staging tables. |
Database pooling |
✅ |
Supports connection pooling for efficient resource utilization across multiple pipelines. |
Source persisted internal cache |
N/A |
State lives in Core Hub metadata; publisher keeps no disk cache. |
Target persisted internal cache |
N/A |
Messages are pushed straight to Pub/Sub; no local buffering. |
Driver / connector |
Google Pub/Sub Java SDK |
Authenticated via IAM service accounts/roles. |
Chains |
N/A |
Target-only connector. |
Truncate operation support (reading) |
N/A |
Target-only connector. |
Truncate operation support (writing) |
N/A |
Pub/Sub topics are append-only; agent does not delete messages. |