Two-way sync
Changes in CockroachDB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep CockroachDB 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 CockroachDB.
Stacksync mirrors Cases, Products, Work Orders, Work Details from Servicemax into Views, Indexes, Sequences, Changefeeds in CockroachDB 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.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Servicemax are ordinary rows in CockroachDB; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in CockroachDB and Stacksync propagates the change into Servicemax, replacing custom integration code.
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.
| CockroachDB objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Databases Logical containers a sync connects to, addressed like PostgreSQL databases. | 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. | Databases is specific to CockroachDB and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to isolate synced tables from application tables. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Schemas is specific to CockroachDB and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Tables The core read/write target; rows sync bi-directionally with SaaS objects or other databases. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Tables is specific to CockroachDB and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Views Read-only projections used as curated sync sources. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Views is specific to CockroachDB and Stock History to Servicemax — each maps to any object or custom field on the other side. | |
| Indexes Secondary indexes that keep sync lookup queries fast on key columns. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Indexes is specific to CockroachDB and Accounts to Servicemax — each maps to any object or custom field on the other side. | |
| Sequences ID generators that matter when writes originate from an external system. | Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Sequences is specific to CockroachDB and Contacts 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 CockroachDB are captured at the source via change data capture — no polling loop against its API. CDC via changefeeds, which stream row-level changes.
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 CockroachDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every CockroachDB–Servicemax connection.
Changes in CockroachDB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever CockroachDB 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 CockroachDB or Servicemax record.
Track your CockroachDB ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between CockroachDB 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 CockroachDB 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 CockroachDB 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 CockroachDB and Servicemax: authenticate both systems, choose the objects to sync (such as CockroachDB's Databases and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 CockroachDB and Servicemax: One integration pattern for the whole stack; Read Servicemax with a query; Automate Servicemax from your codebase. Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
CockroachDB: SQL wire protocol (PostgreSQL-compatible). Authentication: Database credentials with TLS; client certificates or SCRAM password auth. 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: Syncs consume the Salesforce org-wide daily API allocation shared by every integration; it varies by edition and license count. CockroachDB: Changefeeds provide native CDC, streaming row-level changes to sinks such as Kafka, cloud storage, or webhook endpoints. Stacksync's field mapping accounts for these differences between CockroachDB 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 CockroachDB and Servicemax records are not retained after a sync operation.
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 448 integrations available for CockroachDB and Servicemax.