Skip to content
Database

Elasticsearch to Google Cloud Spanner integration — real-time, two-way sync

Keep Elasticsearch and Google Cloud Spanner 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 Elasticsearch and Google Cloud Spanner

Keep Elasticsearch and Google Cloud Spanner synchronized in real time, across engines, regions, or services, in one or both directions.

Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.

Stacksync syncs tables or collections between Elasticsearch and Google Cloud Spanner continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.

Common use cases

  • 01 Push product catalog data from an ERP or commerce database into Elasticsearch for storefront search.
  • 02 Mirror support tickets into an index used for full-text search and agent-assist tooling.
  • 03 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.
  • 04 Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.

Common sync patterns

Regional or environment copies

Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.

Cross-engine sync

Keep the same dataset live in both Elasticsearch and Google Cloud Spanner, so each workload runs on the engine that suits it.

Migration with zero-downtime cutover

When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.

What you can sync between Elasticsearch and Google Cloud Spanner

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.

Elasticsearch objects Google Cloud Spanner objects How this pairing syncs
Indices Target containers for synced records; each holds a table-like collection of JSON documents. Interleaved tables Child rows physically co-located with parents; synced as related records. Indices is specific to Elasticsearch and Interleaved tables to Google Cloud Spanner — each maps to any object or custom field on the other side.
Documents The unit of sync; JSON records created, updated, and deleted by _id. Secondary indexes Used to make incremental read queries efficient on non-key columns. Documents is specific to Elasticsearch and Secondary indexes to Google Cloud Spanner — each maps to any object or custom field on the other side.
Index mappings Field type definitions that determine how synced fields are indexed and queried. Change streams Capture inserts, updates, and deletes for log-style change data capture. Index mappings is specific to Elasticsearch and Change streams to Google Cloud Spanner — each maps to any object or custom field on the other side.
Aliases Stable read/write names that let a sync cut over between index versions without downtime. Views Read-only projections useful for shaping data before it leaves Spanner. Aliases is specific to Elasticsearch and Views to Google Cloud Spanner — each maps to any object or custom field on the other side.
Data streams Append-only targets for time-series or event data pushed from source systems. Databases Top-level containers that scope schema and sync configuration. Data streams is specific to Elasticsearch and Databases to Google Cloud Spanner — each maps to any object or custom field on the other side.
Ingest pipelines Server-side transforms applied to documents as a sync writes them. Tables Relational tables mapped one-to-one to sync targets. Ingest pipelines is specific to Elasticsearch and Tables to Google Cloud Spanner — each maps to any object or custom field on the other side.

How changes propagate between Elasticsearch and Google Cloud Spanner

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.

Elasticsearch Google Cloud Spanner Interval-based propagation

DetectionStacksync polls Elasticsearch for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or sequence fields.

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

Google Cloud Spanner Elasticsearch Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

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

Rate-limit considerations

  • Elasticsearch: No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity.
  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
What ships with Elasticsearch ⇄ Google Cloud Spanner

Connect Elasticsearch and Google Cloud Spanner for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–Google Cloud Spanner connection.

Real-time

Two-way sync

Changes in Elasticsearch or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Elasticsearch or Google Cloud Spanner 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 Elasticsearch or Google Cloud Spanner record.

Observability

Monitoring

Track your Elasticsearch ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Elasticsearch and Google Cloud Spanner.

How the Elasticsearch and Google Cloud Spanner connectors work

Elasticsearch

Integration surface
REST API (JSON over HTTP)
Authentication
API keys or basic authentication; Elastic Cloud also issues service account tokens
Change detection
Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks
Capabilities
read · write
Rate limits
No fixed request quota; throughput is bounded by cluster sizing, thread pools, and bulk queue capacity

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
How it works

How to connect Elasticsearch to Google Cloud Spanner — 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 Elasticsearch and Google Cloud Spanner 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
    Elasticsearch connected
    Google Cloud Spanner connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Elasticsearch and Google Cloud Spanner 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 · Elasticsearch ⇄ Google Cloud Spanner
    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
    Elasticsearch Google Cloud Spanner
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Elasticsearch and Google Cloud Spanner 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 441 integrations available for Elasticsearch and Google Cloud Spanner.

Popular · 6 of 441
All Elasticsearch integrations All Google Cloud Spanner 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