Skip to content
Data warehouse ⇄ Storage

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

Keep Apache Druid and Egnyte 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 Egnyte

Bridge query-ready tables and stored files: Apache Druid and Egnyte keep the same records in step, in real time, in both directions.

Apache Druid keeps the tables and query results a business reports on; Egnyte keeps the raw files, documents, and objects that the same business produces and shares. The two overlap wherever a dataset lives as both — a file dropped in Egnyte that has to become rows in Apache Druid, or a result in Apache Druid that people downstream need back as a file in Egnyte. When that overlap is bridged by manual export and import or an overnight job, one side spends the day working from a stale copy.

Stacksync syncs Ingestion Supervisors, Lookups, Tasks, Datasources in Apache Druid with Files, Folders, Users, Groups in Egnyte field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

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 Provision and deprovision Egnyte Users and Groups from an HRIS or IdP so folder access follows employee onboarding and offboarding.
  • 04 Two-way sync of Files and Folders between Egnyte and an operational database or another content store, keeping the folder hierarchy aligned.

Common sync patterns

Where Egnyte is the shared drive: publish results back as files

Curated tables and query results from Apache Druid are written to Egnyte as files the rest of the business can open, keeping the shared copy current without a hand-run export.

One dataset, kept consistent both ways

Where the same dataset lives as a file in Egnyte and a table in Apache Druid, a change on either side propagates to the other, ending the drift between the file people read and the table people query.

Where Egnyte holds the file inventory: make it queryable

The catalog of documents, owners, and folders in Egnyte appears as Ingestion Supervisors, Lookups, Tasks, Datasources in Apache Druid, so file metadata can be joined against the rest of your data and reported on.

What you can sync between Apache Druid and Egnyte

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 Egnyte objects How this pairing syncs
Lookups Key-value mappings joined at query time, refreshable from external systems. Users Accounts managed via the Users API; provisioned, updated, and deactivated in sync with an HRIS or identity provider. Lookups is specific to Apache Druid and Users to Egnyte — each maps to any object or custom field on the other side.
Tasks Batch ingestion and compaction jobs monitored during data loads. Groups Groups and membership managed via the Groups API; kept aligned with directory or IdP groups that drive folder access. Tasks is specific to Apache Druid and Groups to Egnyte — 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. Permissions Folder permissions listed, set, and removed via the Permissions API; effective permission for a user/folder is computable. Datasources is specific to Apache Druid and Permissions to Egnyte — each maps to any object or custom field on the other side.
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Links Shared file and folder links created, listed, and revoked via the Links API; useful for governing and auditing external sharing. Segments is specific to Apache Druid and Links to Egnyte — 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. Metadata Custom metadata keys and project fields on files/folders via the Metadata API; written for classification and read back for reporting. Dimensions is specific to Apache Druid and Metadata to Egnyte — each maps to any object or custom field on the other side.
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Events and Audit reports File, login, permission, and sharing activity read via the Events API and Audit Reporting API; consumed read-only for compliance. Metrics is specific to Apache Druid and Events and Audit reports to Egnyte — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid and Egnyte

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

Egnyte Apache Druid Sub-second propagation

DetectionEgnyte notifies Stacksync of record changes through webhook events. Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata,.

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.
  • Egnyte: Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request.
What ships with Apache Druid ⇄ Egnyte

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Druid or Egnyte 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 Egnyte record.

Observability

Monitoring

Track your Apache Druid ⇄ Egnyte 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 Egnyte.

How the Apache Druid and Egnyte 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

Egnyte

Integration surface
REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints
Authentication
OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header
Change detection
Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata, permission, and comment events
Capabilities
read · write · webhooks
Rate limits
Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request
How it works

How to connect Apache Druid to Egnyte — 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 Egnyte 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
    Egnyte connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid and Egnyte 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 ⇄ Egnyte
    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 Egnyte
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Druid and Egnyte 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 431 integrations available for Apache Druid and Egnyte.

Popular · 7 of 431
All Apache Druid integrations All Egnyte 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