Real-time
Two-way sync
Changes in Google Pubsub or SAP Hana instantly reflect in both systems. No stale data, no manual imports.
Developer tools ⇄ Database
Google Pubsub to SAP Hana integration — real-time, two-way sync
Keep Google Pubsub and SAP Hana 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 Google Pubsub and SAP Hana
Keep SAP Hana and Google Pubsub in step: the rows in your database and the Dead-letter topics, Ordering keys, Topics, Subscriptions your engineering tools track stay consistent in real time, in both directions.
SAP Hana is where your application's durable data lives; Google Pubsub is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.
Stacksync syncs System-versioned temporal tables, System views (SYS schema), Column store tables, Row store tables in SAP Hana with Dead-letter topics, Ordering keys, Topics, Subscriptions in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.
Common use cases
- 01 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
- 02 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.
- 03 Bridge order or billing events off a topic into an ERP or ticketing system as they arrive, mapping message attributes to target fields.
- 04 Attach an Avro or Protocol Buffer schema to a topic so every message Stacksync publishes is validated against an agreed contract.
Common sync patterns
React to changes on either side in near real time
Updates in Google Pubsub arrive as row changes in SAP Hana, and writes to SAP Hana propagate to Google Pubsub within seconds, so triggers, jobs, and alerts fire without polling.
Where Google Pubsub manages users or groups: keep identity aligned
Directory and identity records in Google Pubsub stay matched to the users or owners table in SAP Hana, so provisioning and de-provisioning flow from one source.
Turn rows into the records your tools track
A new or changed row in SAP Hana creates or updates the matching record in Google Pubsub, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.
What you can sync between Google Pubsub and SAP Hana
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.
| Google Pubsub objects | SAP Hana objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Avro or Protocol Buffer definitions bound to a topic; validate that every published message matches the agreed structure. | Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Ordering keys Tag messages so those sharing a key deliver in publish order when message ordering is enabled; throughput capped at 1 MBps per key. | Column store tables HANA's default table type, optimized for analytics; synced two-way as rows over the SQL interface with the primary key driving upserts and delete tracking. | Ordering keys is specific to Google Pubsub and Column store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. | Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. | Topics is specific to Google Pubsub and Row store tables to SAP Hana — each maps to any object or custom field on the other side. | |
| Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. | Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. | Subscriptions is specific to Google Pubsub and Calculation views to SAP Hana — each maps to any object or custom field on the other side. | |
| Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. | SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. | Messages is specific to Google Pubsub and SQL views to SAP Hana — each maps to any object or custom field on the other side. | |
| Snapshots Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time. | Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. | Snapshots is specific to Google Pubsub and Sequences to SAP Hana — each maps to any object or custom field on the other side. |
How changes propagate between Google Pubsub and SAP Hana
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.
Google Pubsub SAP Hana 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 SAP Hana as a row-level write, with types converted between the two schemas.
SAP Hana Google Pubsub Sub-second propagation
DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.
DeliveryEach detected change is written to Google Pubsub through its API, with automatic retries and rate-limit backoff.
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.
- SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Google Pubsub ⇄ SAP Hana
Connect Google Pubsub and SAP Hana for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Pubsub–SAP Hana connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Google Pubsub or SAP Hana 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 Google Pubsub or SAP Hana record.
Observability
Monitoring
Track your Google Pubsub ⇄ SAP Hana sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Google Pubsub and SAP Hana.
How the Google Pubsub and SAP Hana connectors work
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
SAP Hana
- Integration surface
- SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
- Authentication
- Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
- Change detection
- Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
- Capabilities
- read · write · CDC
- Rate limits
- No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works
How to connect Google Pubsub to SAP Hana — 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.
- 01
Connect your apps
Authenticate Google Pubsub and SAP Hana with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Google Pubsub
connected
SAP Hana
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Google Pubsub and SAP Hana 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.
objects · Google Pubsub ⇄ SAP HanaCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Google Pubsub SAP HanaCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Google Pubsub and SAP Hana integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Google Pubsub and SAP Hana: authenticate both systems, choose the objects to sync (such as Google Pubsub's Schemas and Ordering keys), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Google Pubsub: 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. On SAP Hana: Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the SAP Hana side: System-versioned temporal tables, System views (SYS schema), Column store tables, Row store tables, plus custom fields where SAP Hana exposes them. On the Google Pubsub side: Dead-letter topics, Ordering keys, Topics, Subscriptions. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Google Pubsub and SAP Hana: React to changes on either side in near real time; Where Google Pubsub manages users or groups: keep identity aligned; Turn rows into the records your tools track. Updates in Google Pubsub arrive as row changes in SAP Hana, and writes to SAP Hana propagate to Google Pubsub within seconds, so triggers, jobs, and alerts fire without polling.
-
Google Pubsub: 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. SAP Hana: SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access. Authentication: Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting. Stacksync manages authentication, retries, and rate limits on both sides.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 352 integrations available for Google Pubsub and SAP Hana.
Popular · 5 of 352
No integrations match .
