Two-way sync
Changes in Google Cloud Spanner or Ukg Ready instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner and Ukg Ready in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Ukg Ready is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Google Cloud Spanner is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Reports (Report-as-a-Service), Employees, Employment / Positions, Compensation in Ukg Ready need to exist as queryable Rows, Interleaved tables, Secondary indexes, Change streams in Google Cloud Spanner before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Rows, Interleaved tables, Secondary indexes, Change streams in Google Cloud Spanner with Reports (Report-as-a-Service), Employees, Employment / Positions, Compensation in Ukg Ready field by field, in real time. You decide which system owns which fields — Ukg Ready typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Reports (Report-as-a-Service), Employees, Employment / Positions, Compensation replicate into Google Cloud Spanner where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Ukg Ready stay consistent in Google Cloud Spanner, so hierarchy-driven logic and permissions don't drift.
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.
| Google Cloud Spanner objects | Ukg Ready objects | How this pairing syncs | |
|---|---|---|---|
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | Payroll (Earnings / Deductions / Employee Payroll Runs) Earnings and deductions can be imported into pay runs; Employee Payroll Runs (gross, net, taxes) read back for GL posting and analytics. | Secondary indexes is specific to Google Cloud Spanner and Payroll (Earnings / Deductions / Employee Payroll Runs) to Ukg Ready — each maps to any object or custom field on the other side. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Benefits Plan enrollments, coverage tiers, contributions, and effective dates; typically read into benefits or finance systems. | Change streams is specific to Google Cloud Spanner and Benefits to Ukg Ready — each maps to any object or custom field on the other side. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Cost Centers / Groups Departments, locations, and hierarchy used as org structure; read to align headcount and budget models across systems. | Views is specific to Google Cloud Spanner and Cost Centers / Groups to Ukg Ready — each maps to any object or custom field on the other side. | |
| Databases Top-level containers that scope schema and sync configuration. | Reports (Report-as-a-Service) Scheduled IBM Cognos extracts used for bulk historical pulls that the per-employee REST endpoints are not built for. | Databases is specific to Google Cloud Spanner and Reports (Report-as-a-Service) to Ukg Ready — each maps to any object or custom field on the other side. | |
| Tables Relational tables mapped one-to-one to sync targets. | Employees Core person records (demographics, contact info, status, work location); synced two-way and mapped to HRIS or person tables in a database. | Tables is specific to Google Cloud Spanner and Employees to Ukg Ready — each maps to any object or custom field on the other side. | |
| Rows The unit of read and write in each sync cycle, keyed by primary key. | Employment / Positions Job title, department, employment type, hire and termination dates; read for org modeling and written when roles change. | Rows is specific to Google Cloud Spanner and Employment / Positions to Ukg Ready — 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 Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.
DeliveryEach detected change is written to Ukg Ready through its API, with automatic retries and rate-limit backoff.
DetectionUkg Ready notifies Stacksync of record changes through webhook events. UKG Webhooks for select events (employee.created, employee.updated, account/org changes) with HMAC signing.
DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Ukg Ready connection.
Changes in Google Cloud Spanner or Ukg Ready instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or Ukg Ready data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Spanner or Ukg Ready record.
Track your Google Cloud Spanner ⇄ Ukg Ready sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Ukg Ready.
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 Google Cloud Spanner and Ukg Ready 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 Google Cloud Spanner and Ukg Ready 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 Google Cloud Spanner and Ukg Ready: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Secondary indexes and Change streams), map fields visually, and changes propagate both ways in milliseconds — no code required.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Ukg Ready: UKG Ready REST API (v1/v2) plus the Import Tool (XML transactions) and Report-as-a-Service (IBM Cognos); a legacy SOAP API also exists. Authentication: A 7-digit company short name, a Web API key (Company Setup > Login Config), and a dedicated API service-account user (username/password) are exchanged for a session Bearer token sent on every request; Onboarding/Recruiting endpoints use a separate authorization token. Stacksync manages authentication, retries, and rate limits on both sides.
Google Cloud Spanner: It supports two SQL dialects: GoogleSQL and a PostgreSQL-interface dialect chosen at database creation. Ukg Ready: REST endpoints are oriented around per-employee reads and updates, so bulk historical extracts commonly run through Report-as-a-Service (IBM Cognos) instead of row-by-row calls. Stacksync's field mapping accounts for these differences between Google Cloud Spanner and Ukg Ready 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 Google Cloud Spanner and Ukg Ready records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Google Cloud Spanner and Ukg Ready connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Google Cloud Spanner–Ukg Ready integration in-house.
Yes — Stacksync ships production-grade connectors for both Google Cloud Spanner and Ukg Ready. 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 427 integrations available for Google Cloud Spanner and Ukg Ready.