Two-way sync
Changes in Elasticsearch or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Keep Elasticsearch and TimescaleDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 TimescaleDB 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.
Keep the same dataset live in both Elasticsearch and TimescaleDB, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
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 | TimescaleDB objects | |
|---|---|---|
| Data streams Append-only targets for time-series or event data pushed from source systems. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | |
| Ingest pipelines Server-side transforms applied to documents as a sync writes them. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | |
| Index templates Reusable settings and mappings applied automatically to new indices a sync creates. | Views Standard SQL views used to shape or filter data for consumers. | |
| Indices Target containers for synced records; each holds a table-like collection of JSON documents. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | |
| Documents The unit of sync; JSON records created, updated, and deleted by _id. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | |
| Index mappings Field type definitions that determine how synced fields are indexed and queried. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–TimescaleDB connection.
Changes in Elasticsearch or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Elasticsearch or TimescaleDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Elasticsearch or TimescaleDB record.
Track your Elasticsearch ⇄ TimescaleDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Elasticsearch and TimescaleDB.
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.
Authenticate Elasticsearch and TimescaleDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Elasticsearch and TimescaleDB 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Elasticsearch and TimescaleDB: authenticate both systems, choose the objects to sync (such as Elasticsearch's Data streams and Ingest pipelines), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Elasticsearch: Polling on timestamp or sequence fields; Elasticsearch does not expose a native change feed or webhooks. On TimescaleDB: Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Elasticsearch side: Ingest pipelines, Index templates, Indices, Documents, plus custom fields where Elasticsearch exposes them. On the TimescaleDB side: Schemas, Hypertables, Chunks, Continuous Aggregates. 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 Elasticsearch and TimescaleDB: Cross-engine sync; Migration with zero-downtime cutover; Shared reference data between services. Keep the same dataset live in both Elasticsearch and TimescaleDB, so each workload runs on the engine that suits it.
Elasticsearch: REST API (JSON over HTTP). Authentication: API keys or basic authentication; Elastic Cloud also issues service account tokens. TimescaleDB: SQL wire protocol (PostgreSQL). Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Elasticsearch and TimescaleDB.