Two-way sync
Changes in CockroachDB or Easypost instantly reflect in both systems. No stale data, no manual imports.
Keep CockroachDB and Easypost in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.
Stacksync mirrors Rate, Tracker, Batch, CarrierAccount from Easypost into CockroachDB and keeps both sides consistent in real time. Whatever Easypost holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in CockroachDB, such as new prices, stock levels, or fulfillment status, sync back into Easypost with its validations respected.
Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.
Prices, stock levels, or product details maintained in CockroachDB sync back onto Easypost, so the storefront shows what your systems treat as true.
Orders and their status become rows in CockroachDB for routing, fulfillment, and reporting, without polling the platform.
Choose exactly which tables and fields may flow from CockroachDB back into Easypost, keeping the store authoritative on what it owns.
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 | Easypost objects | How this pairing syncs | |
|---|---|---|---|
| Views Read-only projections used as curated sync sources. | Shipment The central writable object: create with a to/from Address and Parcel, receive Rate options, then buy a label to get postage_label and tracking_code; retrieve and list with cursor pagination. | Views is specific to CockroachDB and Shipment to Easypost — each maps to any object or custom field on the other side. | |
| Indexes Secondary indexes that keep sync lookup queries fast on key columns. | Address Origin and destination locations; create, retrieve, and list, plus address verification (delivery and residential) to normalize and validate addresses before they are saved downstream. | Indexes is specific to CockroachDB and Address to Easypost — each maps to any object or custom field on the other side. | |
| Sequences ID generators that matter when writes originate from an external system. | Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. | Sequences is specific to CockroachDB and Parcel to Easypost — each maps to any object or custom field on the other side. | |
| Changefeeds Built-in CDC streams that emit row-level changes to external sinks. | Rate Carrier service and price options EasyPost generates on a Shipment; read-only - you select a rate id and buy it, you do not create or edit rates directly. | Changefeeds is specific to CockroachDB and Rate to Easypost — each maps to any object or custom field on the other side. | |
| Databases Logical containers a sync connects to, addressed like PostgreSQL databases. | Tracker Tracking for a shipment by tracking_code and carrier; create a Tracker to begin tracking, read status and tracking_details, and receive tracker.updated events via webhook as the parcel moves. | Databases is specific to CockroachDB and Tracker to Easypost — 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. | Batch Bulk shipment processing; create a batch, add or remove shipments, buy all labels at once, and generate a consolidated label or ScanForm for the day's orders. | Schemas is specific to CockroachDB and Batch to Easypost — 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 Easypost through its API, with automatic retries and rate-limit backoff.
DetectionEasypost notifies Stacksync of record changes through webhook events. Webhooks deliver an Event via HTTP POST on object changes (e.g.
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–Easypost connection.
Changes in CockroachDB or Easypost instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever CockroachDB or Easypost 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 Easypost record.
Track your CockroachDB ⇄ Easypost sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between CockroachDB and Easypost.
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 Easypost 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 Easypost 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 Easypost: authenticate both systems, choose the objects to sync (such as CockroachDB's Views and Indexes), 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 Easypost: Keep catalog and inventory current; Order data where your code can use it; Controlled write-back. Prices, stock levels, or product details maintained in CockroachDB sync back onto Easypost, so the storefront shows what your systems treat as true.
CockroachDB: SQL wire protocol (PostgreSQL-compatible). Authentication: Database credentials with TLS; client certificates or SCRAM password auth. Easypost: REST API (EasyPost API v2, https://api.easypost.com/v2). Authentication: HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys. Stacksync manages authentication, retries, and rate limits on both sides.
CockroachDB: CockroachDB speaks the PostgreSQL wire protocol, so standard Postgres drivers and tooling connect without modification. Easypost: Test and Production API keys are separate: test-mode calls do not create real labels or charges, so integration tests and dry-run backfills should run against the test key before touching production. Stacksync's field mapping accounts for these differences between CockroachDB and Easypost 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 Easypost 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 401 integrations available for CockroachDB and Easypost.