Two-way sync
Changes in Apache Druid or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and Oracle Fusion Cloud HCM 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 Oracle Fusion Cloud HCM 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 Positions, Departments (Organizations), Locations, Grades and Salaries from Oracle Fusion Cloud HCM 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 Oracle Fusion Cloud HCM 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 Oracle Fusion Cloud HCM, where the HR team sees them in the system they already use.
People and organization records from Oracle Fusion Cloud HCM arrive in Apache Druid as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Analysts combine Oracle Fusion Cloud HCM'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 | Oracle Fusion Cloud HCM objects | How this pairing syncs | |
|---|---|---|---|
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Locations Physical work locations referenced by assignments; synced so downstream provisioning and directory tools resolve the same location codes. | Datasources is specific to Apache Druid and Locations to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Grades and Salaries Grade, grade-rate, and worker compensation records; usually read out for compensation and headcount analytics, and written back for corrections. | Segments is specific to Apache Druid and Grades and Salaries to Oracle Fusion Cloud HCM — 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. | Absences (workerAbsenceEntries) Time-off and leave entries; synced into scheduling or workforce-management databases for coverage planning. | Dimensions is specific to Apache Druid and Absences (workerAbsenceEntries) to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Workers (publicWorkers) Person master with personNumber, names, national IDs, and work relationships; synced two-way via the /workers resource, which replaced the desupported /emps resource. | Metrics is specific to Apache Druid and Workers (publicWorkers) to Oracle Fusion Cloud HCM — 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. | Assignments Child of a worker's work relationship carrying job, position, department, location, grade, and manager; effective-dated, so writes go through PATCH with an effective date. | Ingestion Supervisors is specific to Apache Druid and Assignments to Oracle Fusion Cloud HCM — each maps to any object or custom field on the other side. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Jobs Job catalog reference data; commonly read out to align titles and job codes in a warehouse or written to keep downstream systems consistent. | Lookups is specific to Apache Druid and Jobs to Oracle Fusion Cloud HCM — 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 Oracle Fusion Cloud HCM through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Oracle Fusion Cloud HCM are captured at the source via change data capture — no polling loop against its API. Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change).
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–Oracle Fusion Cloud HCM connection.
Changes in Apache Druid or Oracle Fusion Cloud HCM instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or Oracle Fusion Cloud HCM 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 Oracle Fusion Cloud HCM record.
Track your Apache Druid ⇄ Oracle Fusion Cloud HCM sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and Oracle Fusion Cloud HCM.
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 Oracle Fusion Cloud HCM 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 Oracle Fusion Cloud HCM 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 Oracle Fusion Cloud HCM: authenticate both systems, choose the objects to sync (such as Apache Druid's Datasources and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Apache Druid: Rollup can pre-aggregate events at ingestion time, meaning the stored granularity may differ from the raw event stream. Oracle Fusion Cloud HCM: Assignments are date-effective; reads and writes must specify an effective date, and updates create new date-effective rows rather than overwriting history. Stacksync's field mapping accounts for these differences between Apache Druid and Oracle Fusion Cloud HCM 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 Apache Druid and Oracle Fusion Cloud HCM records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Apache Druid and Oracle Fusion Cloud HCM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Druid–Oracle Fusion Cloud HCM integration in-house.
Yes — Stacksync ships production-grade connectors for both Apache Druid and Oracle Fusion Cloud HCM. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Apache Druid: Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates. On Oracle Fusion Cloud HCM: Atom feeds expose changes-only feeds for key events (new hire, termination, assignment change); REST q= filters on LastUpdateDate and HCM Extract in incremental mode cover broader deltas. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 439 integrations available for Apache Druid and Oracle Fusion Cloud HCM.