Skip to content
Data warehouse ⇄ Developer tools

ClickHouse to Google Pubsub integration — real-time, two-way sync

Keep ClickHouse and Google Pubsub in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect ClickHouse and Google Pubsub

Close the gap between analytics and operations: ClickHouse holds the record while Google Pubsub runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

ClickHouse is the central store where teams keep Databases, Views, Materialized views, Distributed tables for reporting and analysis; Google Pubsub runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Messages, Schemas, Snapshots, Message attributes produced in Google Pubsub are exactly what analysts want to measure in ClickHouse, and the curated rows in ClickHouse are what should drive the next action in Google Pubsub. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Databases, Views, Materialized views, Distributed tables in ClickHouse with Messages, Schemas, Snapshots, Message attributes in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
  • 02 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • 03 Publish new and changed database rows as messages to a Pub/Sub topic so multiple downstream subscriptions consume the change stream independently.
  • 04 Consume messages from a subscription via StreamingPull and write them into a Postgres or warehouse table for durable, SQL-queryable storage.

Common sync patterns

No batch jobs to babysit

New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.

One shared record, kept consistent

Where both systems track the same entity, a change on either side propagates to the other, ending the manual reconciliation between the operational copy and the warehouse copy.

Keep user and access records aligned

Where Google Pubsub manages users, directory, or access data, those records stay current in ClickHouse — and can be provisioned back from it — so ownership and permissions match across both.

What you can sync between ClickHouse and Google Pubsub

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

ClickHouse objects Google Pubsub objects How this pairing syncs
Distributed tables Query-routing tables over cluster shards in self-managed deployments. Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. Distributed tables is specific to ClickHouse and Topics to Google Pubsub — each maps to any object or custom field on the other side.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. Dictionaries is specific to ClickHouse and Subscriptions to Google Pubsub — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. Tables (MergeTree family) is specific to ClickHouse and Messages to Google Pubsub — each maps to any object or custom field on the other side.
Databases Namespaces that group tables and scope permissions for sync users. Schemas Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure. Databases is specific to ClickHouse and Schemas to Google Pubsub — each maps to any object or custom field on the other side.
Views Saved queries used as curated, read-only sync sources. Snapshots Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time. Views is specific to ClickHouse and Snapshots to Google Pubsub — each maps to any object or custom field on the other side.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Message attributes Up to 100 key-value pairs per message; carry routing metadata and drive subscription filter expressions. Materialized views is specific to ClickHouse and Message attributes to Google Pubsub — each maps to any object or custom field on the other side.

How changes propagate between ClickHouse and Google Pubsub

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

ClickHouse Google Pubsub Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

DeliveryEach detected change is written to Google Pubsub through its API, with automatic retries and rate-limit backoff.

Google Pubsub ClickHouse Sub-second propagation

DetectionGoogle Pubsub notifies Stacksync of record changes through webhook events. Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST.

DeliveryEach detected change is applied to ClickHouse as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Pubsub: Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key.
What ships with ClickHouse ⇄ Google Pubsub

Connect ClickHouse and Google Pubsub for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Google Pubsub connection.

Real-time

Two-way sync

Changes in ClickHouse or Google Pubsub instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever ClickHouse or Google Pubsub data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single ClickHouse or Google Pubsub record.

Observability

Monitoring

Track your ClickHouse ⇄ Google Pubsub sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between ClickHouse and Google Pubsub.

How the ClickHouse and Google Pubsub connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

Google Pubsub

Integration surface
REST and gRPC (Cloud Pub/Sub API v1)
Authentication
Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber
Change detection
Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST; no modified-date polling
Capabilities
read · write · webhooks
Rate limits
Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key
How it works

How to connect ClickHouse to Google Pubsub — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate ClickHouse and Google Pubsub with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    ClickHouse connected
    Google Pubsub connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the ClickHouse and Google Pubsub objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · ClickHouse ⇄ Google Pubsub
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    ClickHouse Google Pubsub
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

ClickHouse and Google Pubsub integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 352 integrations available for ClickHouse and Google Pubsub.

Popular · 6 of 352
All ClickHouse integrations All Google Pubsub integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own