Two-way sync
Changes in Apache Cassandra or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Cassandra 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 Apache Cassandra.
Stacksync mirrors Products, Work Orders, Work Details, Installed Products from Servicemax into Tables, Partitions and Rows, Materialized Views, Secondary Indexes in Apache Cassandra 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 Apache Cassandra; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in Apache Cassandra and Stacksync propagates the change into Servicemax, replacing custom integration code.
Updates in Servicemax arrive as row changes in Apache Cassandra, 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.
| Apache Cassandra objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Secondary Indexes Optional indexes that allow filtered reads outside the partition key. | 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. | Secondary Indexes is specific to Apache Cassandra and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| User-Defined Types Composite column types that syncs must flatten or map to structured fields. | 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. | User-Defined Types is specific to Apache Cassandra and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Collections List, set, and map columns handled with type-aware field mapping. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Collections is specific to Apache Cassandra and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Counters Increment-only counter columns, usually read-only in syncs. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Counters is specific to Apache Cassandra and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Keyspaces Top-level namespaces with replication settings that scope a sync connection. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Keyspaces is specific to Apache Cassandra and Stock History to Servicemax — each maps to any object or custom field on the other side. | |
| Tables Wide-column tables addressed by partition key, the unit of row-level sync. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Tables is specific to Apache Cassandra and Accounts 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 Apache Cassandra are captured at the source via change data capture — no polling loop against its API. Commit-log based CDC on tables with CDC enabled, or polling using writetime metadata and timestamp columns.
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 written to Apache Cassandra through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Cassandra–Servicemax connection.
Changes in Apache Cassandra or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Cassandra 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 Apache Cassandra or Servicemax record.
Track your Apache Cassandra ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Cassandra 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 Apache Cassandra 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 Apache Cassandra 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 Apache Cassandra and Servicemax: authenticate both systems, choose the objects to sync (such as Apache Cassandra's Secondary Indexes and User-Defined Types), map fields visually, and changes propagate both ways in milliseconds — no code required.
Apache Cassandra: CQL over the Cassandra native binary protocol. Authentication: Database credentials (password authenticator); TLS and role-based grants where configured. Servicemax: Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform). Authentication: Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects. Stacksync manages authentication, retries, and rate limits on both sides.
Servicemax: Polling orders incremental changes by each object's SystemModstamp or LastModifiedDate; objects without a modified timestamp or API write access cannot sync incrementally. Apache Cassandra: Consistency is tunable per operation (for example ONE, QUORUM, ALL), letting syncs trade latency against read/write guarantees. Stacksync's field mapping accounts for these differences between Apache Cassandra and Servicemax 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 Apache Cassandra and Servicemax records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Apache Cassandra and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Cassandra–Servicemax integration in-house.
Yes — Stacksync ships production-grade connectors for both Apache Cassandra and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 435 integrations available for Apache Cassandra and Servicemax.