Two-way sync
Changes in Amazon DynamoDB or Rockset instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon DynamoDB and Rockset in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Amazon DynamoDB's rows in Rockset, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Amazon DynamoDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Amazon DynamoDB sync into Rockset in real time, and result tables in Rockset sync back into Amazon DynamoDB, with schema and type mapping between the two systems handled for you.
Rows from Amazon DynamoDB land in Rockset as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in Rockset sync into Amazon DynamoDB, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
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.
| Amazon DynamoDB objects | Rockset objects | How this pairing syncs | |
|---|---|---|---|
| Global Tables Multi-region, active-active replicas of a table kept in sync by DynamoDB; each region is read and written locally with last-writer-wins conflict resolution. | Virtual Instances Isolated compute units that separate ingest from query workloads. | Global Tables is specific to Amazon DynamoDB and Virtual Instances to Rockset — each maps to any object or custom field on the other side. | |
| Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. | Collections Schemaless document containers that ingested and synced records land in. | Time to Live (TTL) is specific to Amazon DynamoDB and Collections to Rockset — each maps to any object or custom field on the other side. | |
| Tables Top-level containers, each with a partition key and optional sort key; Stacksync syncs a table as a stream of items with full read and write via PutItem, UpdateItem, and DeleteItem. | Documents JSON records addressable by _id, written via the Write API in sync pipelines. | Tables is specific to Amazon DynamoDB and Documents to Rockset — each maps to any object or custom field on the other side. | |
| Items Individual schemaless records (attributes up to 400 KB each); read with GetItem, Query, and Scan and written with PutItem or BatchWriteItem, so write is supported here. | Workspaces Namespaces that group collections and query lambdas per team or environment. | Items is specific to Amazon DynamoDB and Workspaces to Rockset — each maps to any object or custom field on the other side. | |
| Global secondary indexes (GSIs) Alternate key projections that let you Query by non-key attributes without a full table Scan; read-only views maintained automatically by DynamoDB. | Query Lambdas Named, parameterized SQL queries invoked over REST to read synced data. | Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Query Lambdas to Rockset — each maps to any object or custom field on the other side. | |
| Local secondary indexes (LSIs) Extra sort keys within the same partition key, defined at table creation; queried like the base table for alternate access patterns. | Aliases Stable names that point at collections, used to swap datasets without changing queries. | Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Aliases to Rockset — each maps to any object or custom field on the other side. |
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.
DetectionChanges in Amazon DynamoDB are captured at the source via change data capture — no polling loop against its API. DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views.
DeliveryEach detected change is applied to Rockset as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Rockset for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL queries on timestamp fields.
DeliveryEach detected change is applied to Amazon DynamoDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon DynamoDB–Rockset connection.
Changes in Amazon DynamoDB or Rockset instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon DynamoDB or Rockset data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Amazon DynamoDB or Rockset record.
Track your Amazon DynamoDB ⇄ Rockset sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Rockset.
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 Amazon DynamoDB and Rockset 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 Amazon DynamoDB and Rockset 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 Amazon DynamoDB and Rockset: authenticate both systems, choose the objects to sync (such as Amazon DynamoDB's Global Tables and Time to Live (TTL)), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Rockset side: Virtual Instances, Collections, Documents, Workspaces, plus custom fields where Rockset exposes them. On the Amazon DynamoDB side: Tables, Items, Global secondary indexes (GSIs), Local secondary indexes (LSIs). 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 Amazon DynamoDB and Rockset: Operational data in the warehouse, minus the pipeline; Serve warehouse results at database speed; Fresh analytics without loading windows. Rows from Amazon DynamoDB land in Rockset as they change, replacing hand-built CDC and batch extract jobs.
Amazon DynamoDB: AWS SDK / low-level HTTPS JSON API at dynamodb.<region>.amazonaws.com (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan, BatchWriteItem, TransactWriteItems), plus PartiQL (ExecuteStatement) for SQL-style access and DynamoDB Streams for change capture. Authentication: AWS Signature Version 4 (SigV4) signed requests using an IAM access key ID and secret key, or temporary STS credentials from an assumed IAM role; IAM policies scope access down to table and item level. Rockset: REST API (SQL over HTTP, plus a document Write API). Authentication: API key. Stacksync manages authentication, retries, and rate limits on both sides.
Rockset: Its Converged Index stores every field in row, column, and inverted (search) indexes at once, which is why ad-hoc filters and aggregations stay fast without manual index tuning. Amazon DynamoDB: Data is accessed through the AWS SDK JSON API (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan) and, optionally, PartiQL (ExecuteStatement) for SQL-compatible reads and writes. Stacksync's field mapping accounts for these differences between Amazon DynamoDB and Rockset without custom code.
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 534 integrations available for Amazon DynamoDB and Rockset.