Loading
Ongoing maintenance for Salesforce HelpRead More
PHP Vulnerability Monitoring Read More

PCE Active-Active vs Active-Passive DR — Justification

Publish Date: Oct 2, 2026
Description

Anypoint Platform Private Cloud Edition (PCE) does not support a true Active-Active multi-datacenter (DC-DC) high availability architecture. The officially supported and recommended model is Active-Passive (DC-DR), where one cluster is live and a secondary cluster is restored from backup on failover.

Resolution

Why PCE Cannot Run Active-Active Across Datacenters

  1. Single stateful control-plane database per cluster. Every PCE control-plane component (Runtime Manager, Access Management, Exchange, deployment metadata) persists to one Stolon-managed PostgreSQL cluster, plus an object store (SeaweedFS) whose filer metadata is also backed by that same Postgres. Stolon supports one master with local standbys for HA within a cluster — it has no supported multi-region, bidirectional, active-active replication mode.
  2. No conflict resolution for concurrent writes. Running two "active" PCE clusters in separate DCs would mean two independently-writable Postgres instances with no mechanism to reconcile diverging writes (deployments, org config, cluster registration data) between them.
  3. Documented DR model is backup/restore, not live replication. Per the official PCE DR pattern: "Mulesoft Anypoint Private Cloud Edition (PCE) operates via a traditional backup/recovery methodology. A PCE Backup can be used to restore the Application Configuration to a DR Target PCE Cluster." This is inherently Active-Passive — one live cluster at a time, with the DR target stood up only on failover invocation.
  4. Engineering has confirmed there is no supported active-active/dual-active design. In escalation review, engineering stated there is no documented or supported behavior for concurrently-active PCE clusters, and drew a clear line between "officially supported" behavior (documented backup/restore DR) versus unproven configurations that are not treated as defects if they don't behave as active-active.
  5. Consistent with MuleSoft's broader stateful-component guidance across DCs. Related MuleSoft architecture reference material notes that a DR site remains passive (not serving requests) until failure, "as bidirectional active-active synchronization challenges (for Cache, Message Broker or DB) between DC-DR" exist when DCs are in different regions. The same constraint applies to PCE's backend Postgres/object-store layer.
Additional Resources

PCE's control plane relies on a single stateful Postgres/object-store backend per cluster with no supported cross-DC bidirectional replication. The only supported multi-DC pattern is Active-Passive: one live cluster, one warm/cold DR target restored from backup on failover.
True Active-Active DC-DC would require two independently-writable state stores with a conflict-resolution mechanism that MuleSoft does not build or support for PCE

Knowledge Article Number

005460936

 
Loading
Salesforce Help | Article