Two-way sync
Changes in Amazon DynamoDB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon DynamoDB and Servicemax in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers integrate with tools like Servicemax through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Amazon DynamoDB.
Stacksync mirrors Work Orders, Work Details, Installed Products, Service Contracts from Servicemax into Local secondary indexes (LSIs), DynamoDB Streams, Global Tables, Time to Live (TTL) in Amazon DynamoDB and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Servicemax, so the tool and the database never disagree.
Records from Servicemax are ordinary rows in Amazon DynamoDB; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in Amazon DynamoDB and Stacksync propagates the change into Servicemax, replacing custom integration code.
Updates in Servicemax arrive as row changes in Amazon DynamoDB, so triggers, jobs, and services can respond in near real time.
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 | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | DynamoDB Streams is specific to Amazon DynamoDB and Products to Servicemax — each maps to any object or custom field on the other side. | |
| 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. | Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. | Global Tables is specific to Amazon DynamoDB and Work Orders to Servicemax — 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. | Work Details SVMXC__Service_Order_Line__c; line items on a Work Order for labor, parts used, and expenses; read out for billing or written back with usage. | Time to Live (TTL) is specific to Amazon DynamoDB and Work Details to Servicemax — 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. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Tables is specific to Amazon DynamoDB and Installed Products to Servicemax — 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. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Items is specific to Amazon DynamoDB and Service Contracts to Servicemax — 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. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Stock History to Servicemax — 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 written to Servicemax through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.
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–Servicemax connection.
Changes in Amazon DynamoDB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon DynamoDB or Servicemax 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 Servicemax record.
Track your Amazon DynamoDB ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Servicemax.
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 Servicemax 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 Servicemax 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 Servicemax: authenticate both systems, choose the objects to sync (such as Amazon DynamoDB's DynamoDB Streams and Global Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Servicemax 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 Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon DynamoDB–Servicemax integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon DynamoDB and Servicemax. 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 Servicemax: Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Servicemax side: Work Orders, Work Details, Installed Products, Service Contracts, plus custom fields where Servicemax exposes them. On the Amazon DynamoDB side: Local secondary indexes (LSIs), DynamoDB Streams, Global Tables, Time to Live (TTL). Stacksync auto-detects both schemas and converts types between the two systems.
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 543 integrations available for Amazon DynamoDB and Servicemax.