Architecture • iPaaS
Blueprint: High-Availability iPaaS on Netflix Conductor
The Freshworks integration platform now orchestrates 30+ workflows with 99.9% release reliability. This blueprint captures the architecture choices that keep the system resilient.
Control Plane
Conductor acts as the control plane, while workflow definitions live in Git and are promoted via Jenkins pipelines. Every workflow declares:
- Task domains + owners.
- Retry & compensation policy.
- Compliance metadata (PII, PCI tags).
Topology Diagram
The blueprint spans two AWS regions with a federated Conductor control plane. Here is a simplified view.
Data Plane
Execution workers run on Kubernetes with spot + on-demand mix. State synchronization uses DynamoDB global tables plus MySQL read replicas for reporting workloads. CDC pipelines ensure region-to-region parity during migrations.
Reliability Tactics
- Automated runbooks: Conductor events feed PagerDuty and trigger remediation Lambdas.
- Release safety: Jenkins pipelines run contract tests for every workflow + backfill a shadow environment.
- Blast-radius limits: Circuit breakers per task domain halt only the affected integrations.
What Teams Get
Product teams plug into the platform through declarative workflow packs. They gain:
- Telemetry by default (Prometheus + Grafana dashboards).
- Ability to simulate failures via chaos toggles.
- Shared libraries for building adapters in Java or Node.js without reinventing plumbing.
Adoption Journey
We typically guide product teams through a four-stage adoption:
- Model workflows as YAML + define task domains.
- Pair with platform engineers to implement adapters.
- Run contract tests + chaos drills in a sandbox.
- Graduate to production with automated guardrails and SLO dashboards.