Two-way sync
Changes in Apache Druid or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and Ukg Pro in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Ukg Pro is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Apache Druid next to everything else the company measures.
Stacksync syncs Time & Attendance (UTA), Employee (Person Details), Employment Details, Job / Position History from Ukg Pro into tables in Apache Druid continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Apache Druid, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Ukg Pro where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Segments, rollups, or risk flags computed in Apache Druid sync back onto the matching records in Ukg Pro, where the HR team sees them in the system they already use.
People and organization records from Ukg Pro arrive in Apache Druid as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Analysts combine Ukg Pro's workforce records with finance, product, or operational data already in Apache Druid for reporting the HR system cannot produce on its own.
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 Druid objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Ingestion Supervisors is specific to Apache Druid and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Lookups is specific to Apache Druid and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Tasks Batch ingestion and compaction jobs monitored during data loads. | Compensation Details Effective-dated pay rate and salary; usually read into a warehouse for comp reporting and writable as new dated changes through the compensation endpoints. | Tasks is specific to Apache Druid and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Payroll (Pay Statements, Direct Deposit, Earnings) Pay statements, direct-deposit accounts, and earnings history; read-only pay data replicated into finance and warehouse systems for labor-cost reporting. | Datasources is specific to Apache Druid and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Segments is specific to Apache Druid and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Dimensions String and categorical columns used for filtering and grouping in synced queries. | Configuration Setup (Code Tables) Reference data such as jobs, locations, positions, earnings, and deduction codes; used to resolve and validate field values when mapping records during sync. | Dimensions is specific to Apache Druid and Configuration Setup (Code Tables) to Ukg Pro — 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.
DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.
DeliveryEach detected change is written to Ukg Pro through its API, with automatic retries and rate-limit backoff.
DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is applied to Apache Druid as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Ukg Pro connection.
Changes in Apache Druid or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or Ukg Pro 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 Druid or Ukg Pro record.
Track your Apache Druid ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and Ukg Pro.
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 Druid and Ukg Pro 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 Druid and Ukg Pro 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 Druid and Ukg Pro: authenticate both systems, choose the objects to sync (such as Apache Druid's Ingestion Supervisors and Lookups), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Apache Druid side: Ingestion Supervisors, Lookups, Tasks, Datasources, plus custom fields where Apache Druid exposes them. On the Ukg Pro side: Time & Attendance (UTA), Employee (Person Details), Employment Details, Job / Position History. Stacksync auto-detects both schemas and converts types between the two systems.
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 Apache Druid and Ukg Pro: Write-back of computed values; HR data in the warehouse, minus the pipeline; Headcount and cost joined with everything else. Segments, rollups, or risk flags computed in Apache Druid sync back onto the matching records in Ukg Pro, where the HR team sees them in the system they already use.
Apache Druid: REST API (SQL over HTTP and native JSON queries); JDBC via Avatica. Authentication: Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy. Ukg Pro: REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services. Authentication: Core HCM REST APIs use HTTP Basic authentication with a dedicated web service account, plus a Customer API Key and a User API Key sent as headers (found under System Configuration > Security > Service Account Administration); the Onboarding and Recruiting REST APIs instead require a bearer Authorization Token from the token endpoint. Stacksync manages authentication, retries, and rate limits on both sides.
Apache Druid: Druid stores data in immutable, time-partitioned segments; there is no row-level update path, so writes happen through ingestion and reprocessing rather than upserts. Ukg Pro: Writes are modeled as HR events, not raw field edits: new hire (POST), termination (POST with a reason code that must match the tenant's configured reason table), and job or pay changes go through dedicated endpoints rather than a single PATCH. Stacksync's field mapping accounts for these differences between Apache Druid and Ukg Pro without custom code.
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 440 integrations available for Apache Druid and Ukg Pro.