Skip to content
Data warehouse ⇄ Human resources

Apache Druid to Ceridian Dayforce integration — real-time, two-way sync

Keep Apache Druid and Ceridian Dayforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Apache Druid and Ceridian Dayforce

Land the people and organization records from Ceridian Dayforce in Apache Druid as live tables for workforce reporting, without extract jobs, and write computed results back where Ceridian Dayforce can use them.

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 Ceridian Dayforce 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 Org Units, Departments, Jobs & Positions, Time Away From Work & Balances, Employee (HR / Person Details), Employment Status from Ceridian Dayforce 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 Ceridian Dayforce where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Query aggregated event metrics from Druid and sync them into CRM account fields for usage-based selling.
  • 02 Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.
  • 03 React to Dayforce Event Notifications for hire, rehire, and terminate to provision or disable IdP and app access and update downstream records as the changes post.
  • 04 Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.

Common sync patterns

Queryable history for planning and audit

A continuously synced copy in Apache Druid gives you a durable, queryable record of how Ceridian Dayforce's records change over time, for headcount planning and audit questions.

Write-back of computed values

Segments, rollups, or risk flags computed in Apache Druid sync back onto the matching records in Ceridian Dayforce, where the HR team sees them in the system they already use.

HR data in the warehouse, minus the pipeline

People and organization records from Ceridian Dayforce arrive in Apache Druid as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

What you can sync between Apache Druid and Ceridian Dayforce

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 Ceridian Dayforce objects How this pairing syncs
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Org Units, Departments, Jobs & Positions Configuration reference data; POST creates org units and departments and PATCH updates job, position, department, and org-unit data. Used to resolve and validate XRefCodes when mapping employee writes. Datasources is specific to Apache Druid and Org Units, Departments, Jobs & Positions to Ceridian Dayforce — each maps to any object or custom field on the other side.
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Time Away From Work & Balances Time-off requests and accrual balances read per employee; pulled into scheduling, payroll, or absence-reporting databases and used to reconcile leave against downstream systems. Segments is specific to Apache Druid and Time Away From Work & Balances to Ceridian Dayforce — 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. Employee (HR / Person Details) Core worker record keyed by XRefCode; GET Employees returns matching XRefCodes, then a per-employee GET fetches full HR details. New hires are added with POST and edits made with PATCH, so it is read and write. Dimensions is specific to Apache Druid and Employee (HR / Person Details) to Ceridian Dayforce — each maps to any object or custom field on the other side.
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Employment Status Effective-dated employment status and type (active, leave, terminated) that drives active/terminated state for downstream provisioning; read, and writable as new dated status records. Metrics is specific to Apache Druid and Employment Status to Ceridian Dayforce — each maps to any object or custom field on the other side.
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Work Assignments Effective-dated position, department, location, and org-unit assignment; the most-synced record for org charts, provisioning, and analytics. Read and updatable via PATCH. Ingestion Supervisors is specific to Apache Druid and Work Assignments to Ceridian Dayforce — each maps to any object or custom field on the other side.
Lookups Key-value mappings joined at query time, refreshable from external systems. Compensation Summary & Pay Adjustments Compensation Summary returns pay rate and frequency for reporting; Employee Pay Adjustments are written as effective-dated records via PATCH to post pay changes back to Dayforce. Lookups is specific to Apache Druid and Compensation Summary & Pay Adjustments to Ceridian Dayforce — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid and Ceridian Dayforce

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.

Apache Druid Ceridian Dayforce Interval-based propagation

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 Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.

Ceridian Dayforce Apache Druid Sub-second propagation

DetectionCeridian Dayforce 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.

Rate-limit considerations

  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
  • Ceridian Dayforce: Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
What ships with Apache Druid ⇄ Ceridian Dayforce

Connect Apache Druid and Ceridian Dayforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Ceridian Dayforce connection.

Real-time

Two-way sync

Changes in Apache Druid or Ceridian Dayforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Druid or Ceridian Dayforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Apache Druid or Ceridian Dayforce record.

Observability

Monitoring

Track your Apache Druid ⇄ Ceridian Dayforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Druid and Ceridian Dayforce.

How the Apache Druid and Ceridian Dayforce connectors work

Apache Druid

Integration surface
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
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

Ceridian Dayforce

Integration surface
REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads
Authentication
HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account.
Change detection
No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged.
Capabilities
read · write · webhooks
Rate limits
Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
Ceridian Dayforce setup guide
How it works

How to connect Apache Druid to Ceridian Dayforce — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Apache Druid and Ceridian Dayforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Apache Druid connected
    Ceridian Dayforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid and Ceridian Dayforce 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Apache Druid ⇄ Ceridian Dayforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Apache Druid Ceridian Dayforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Druid and Ceridian Dayforce integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 440 integrations available for Apache Druid and Ceridian Dayforce.

Popular · 6 of 440
All Apache Druid integrations All Ceridian Dayforce integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own