Two-way sync
Changes in Amazon DynamoDB or Azure SQL Database instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon DynamoDB and Azure SQL Database 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 Amazon DynamoDB and Azure SQL Database 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.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both Amazon DynamoDB and Azure SQL Database, 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.
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 | Azure SQL Database objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Tables The primary sync target; rows map one-to-one to records in the paired system. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. | Views Read-only projections used when the sync should expose a curated shape rather than raw tables. | Time to Live (TTL) is specific to Amazon DynamoDB and Views to Azure SQL Database — 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. | Schemas Namespaces that organize tables and control which objects a sync user can reach. | Items is specific to Amazon DynamoDB and Schemas to Azure SQL Database — 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. | Rows and columns Standard relational records with typed columns; primary keys anchor upserts. | Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Rows and columns to Azure SQL Database — 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. | Stored procedures Existing business logic that some teams invoke on write instead of direct table inserts. | Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Stored procedures to Azure SQL Database — each maps to any object or custom field on the other side. | |
| DynamoDB Streams Ordered item-level change records (INSERT, MODIFY, REMOVE) with old/new image views and 24-hour retention; the native change-data-capture source Stacksync reads for near-real-time sync. | Change tracking / CDC tables System-maintained change records used to drive incremental sync. | DynamoDB Streams is specific to Amazon DynamoDB and Change tracking / CDC tables to Azure SQL Database — 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 Azure SQL Database as a row-level write, with types converted between the two schemas.
DetectionChanges in Azure SQL Database are captured at the source via change data capture — no polling loop against its API. Change data capture or change tracking, both supported on Azure SQL Database.
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–Azure SQL Database connection.
Changes in Amazon DynamoDB or Azure SQL Database instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon DynamoDB or Azure SQL Database 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 Azure SQL Database record.
Track your Amazon DynamoDB ⇄ Azure SQL Database sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Azure SQL Database.
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 Azure SQL Database 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 Azure SQL Database 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 Azure SQL Database: authenticate both systems, choose the objects to sync (such as Amazon DynamoDB's Tables and Time to Live (TTL)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Amazon DynamoDB: DynamoDB Streams are the native change-data-capture feed: ordered item-level INSERT, MODIFY, and REMOVE records with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views and 24-hour retention. DynamoDB has no HTTP webhooks. Azure SQL Database: It speaks the same TDS protocol as on-premises SQL Server, so existing SQL Server drivers and tools connect without modification. Stacksync's field mapping accounts for these differences between Amazon DynamoDB and Azure SQL Database without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Amazon DynamoDB and Azure SQL Database records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon DynamoDB and Azure SQL Database connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon DynamoDB–Azure SQL Database integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon DynamoDB and Azure SQL Database. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Amazon DynamoDB: DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views and 24-hour retention, read via shard iterators (or Kinesis Data Streams for longer retention). No native HTTP webhooks. On Azure SQL Database: Change data capture or change tracking, both supported on Azure SQL Database; polling as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 475 integrations available for Amazon DynamoDB and Azure SQL Database.