Two-way sync
Changes in Apache Druid or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and Smartrecruiters 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 Smartrecruiters 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 Applications, Jobs, Job Postings, Interviews from Smartrecruiters 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 Smartrecruiters where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
A continuously synced copy in Apache Druid gives you a durable, queryable record of how Smartrecruiters's records change over time, for headcount planning and audit questions.
Segments, rollups, or risk flags computed in Apache Druid sync back onto the matching records in Smartrecruiters, where the HR team sees them in the system they already use.
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 | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Datasources is specific to Apache Druid and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Segments is specific to Apache Druid and Approvals to Smartrecruiters — 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. | Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Dimensions is specific to Apache Druid and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Metrics is specific to Apache Druid and Applications to Smartrecruiters — 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. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Ingestion Supervisors is specific to Apache Druid and Jobs to Smartrecruiters — 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 Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Lookups is specific to Apache Druid and Job Postings to Smartrecruiters — 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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
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–Smartrecruiters connection.
Changes in Apache Druid or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or Smartrecruiters 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 Smartrecruiters record.
Track your Apache Druid ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and Smartrecruiters.
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 Smartrecruiters 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 Smartrecruiters 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 Smartrecruiters: 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: Streaming ingestion from Kafka or Kinesis is managed by supervisors designed to provide exactly-once ingestion semantics. Smartrecruiters: Every response returns rate-limit metadata via X-RateLimit-Limit/Remaining and X-RateLimit-Concurrent-Limit/Remaining headers. Stacksync's field mapping accounts for these differences between Apache Druid and Smartrecruiters 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 Smartrecruiters 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 Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Apache Druid–Smartrecruiters integration in-house.
Yes — Stacksync ships production-grade connectors for both Apache Druid and Smartrecruiters. 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 Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. 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 440 integrations available for Apache Druid and Smartrecruiters.