Skip to content
Data warehouse ⇄ Accounting and finance

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

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

Land the financial records from Zuora in Apache Druid continuously, and write results back, without building or maintaining a pipeline.

Finance data belongs in the warehouse: revenue, invoices, payments, and customers joined with everything else the business measures. Getting it there usually means an extraction pipeline that breaks quietly and delivers yesterday's numbers.

Stacksync syncs Rate Plan and Rate Plan Charge, Product and Product Rate Plan (Product Catalog), Invoice, Payment from Zuora into tables in Apache Druid in real time, and the connection works in both directions: values computed in Apache Druid can be written back to fields in Zuora where you want them operational. Schema changes are handled, API limits are managed, and the sync is something you configure rather than code you maintain.

Common use cases

  • 01 Master the Product Catalog (Products and Product Rate Plans) in a database or PIM and write pricing changes into Zuora.
  • 02 Stream metered Usage records from a warehouse or metering pipeline into Zuora so consumption-based charges are rated on the correct Rate Plan.
  • 03 Keep lookup tables in Druid refreshed from a CRM or database so query-time joins use current reference data.
  • 04 Expose product telemetry stored in Druid to business tools without granting direct cluster access.

Common sync patterns

Finance analytics without ETL

Invoices, payments, and customer records from Zuora arrive in Apache Druid as queryable tables, current within seconds instead of a day behind.

Revenue joined with everything else

Analysts combine Zuora's financial records with product, marketing, or operational data already in Apache Druid for reporting the finance system cannot do alone.

Write-back of computed fields

Scores or segments computed in Apache Druid, like payment-risk flags or customer tiers, sync back onto records in Zuora where the finance team can act on them.

What you can sync between Apache Druid and Zuora

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 Zuora objects How this pairing syncs
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Payment Payment and refund transactions applied against invoices; read for cash application, dunning, and reconciliation reporting in the warehouse. Segments is specific to Apache Druid and Payment to Zuora — 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. Usage Metered consumption records; written into Zuora from a metering or warehouse pipeline so consumption-based charges are rated and invoiced. Dimensions is specific to Apache Druid and Usage to Zuora — each maps to any object or custom field on the other side.
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Order and Amendment Records of subscription create and change actions; written to Zuora to drive quote-to-cash and read for subscription change history. Metrics is specific to Apache Druid and Order and Amendment to Zuora — 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. Account (Billing Account) The customer billing entity holding contacts, payment methods, and billing settings; synced two-way as the parent record most other Zuora objects hang off. Ingestion Supervisors is specific to Apache Druid and Account (Billing Account) to Zuora — each maps to any object or custom field on the other side.
Lookups Key-value mappings joined at query time, refreshable from external systems. Subscription Recurring or usage-based subscription tied to an Account; read for revenue state and written when provisioning or changing plans from a CRM or app. Lookups is specific to Apache Druid and Subscription to Zuora — each maps to any object or custom field on the other side.
Tasks Batch ingestion and compaction jobs monitored during data loads. Rate Plan and Rate Plan Charge The priced components inside a Subscription; synced so charge amounts, quantities, and effective dates stay aligned with the source system. Tasks is specific to Apache Druid and Rate Plan and Rate Plan Charge to Zuora — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid and Zuora

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

Zuora Apache Druid Sub-second propagation

DetectionZuora notifies Stacksync of record changes through webhook events. Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for.

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.
  • Zuora: Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
What ships with Apache Druid ⇄ Zuora

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Zuora

Integration surface
REST API (v1) with Object Query, Data Query, and AQuA bulk export; legacy SOAP API also available
Authentication
OAuth 2.0 client credentials (bearer token, 3600s expiry); access is governed by the Zuora role of the OAuth client's associated user, with no granular scopes
Change detection
Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes
Capabilities
read · write · webhooks
Rate limits
Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
How it works

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

    Choose tables

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

Apache Druid and Zuora 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
CSA STAR
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 435 integrations available for Apache Druid and Zuora.

Popular · 7 of 435
All Apache Druid integrations All Zuora 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