Skip to main content
PreparationZone Logo
PrepZone

MirrorMaker 2 and Multi-Region Replication

Replicate VaultCommerce topics across regions for disaster recovery and read-local consumers.

Pass checkpoint below

Why this matters

  • VaultCommerce mirrors vaultcommerce.orders.* from us-east to eu-west for GDPR-local analytics.
  • MM2 handles offset mapping, topic naming (source.cluster.topic), and consumer group offset sync.
  • DR failover requires runbook for consumer group promotion, not just topic copy.
  • Cross-region replication adds latency and cost — replicate only what regions need.
Primary region
Kafka cluster A
DR region
MirrorMaker 2Replicates topics
Kafka cluster B
MirrorMaker 2 replicates topics from a primary cluster to a DR cluster for failover.

MirrorMaker 2 architecture

Source connector reads from primary cluster; Heartbeat and Checkpoint connectors sync consumer offsets. VaultCommerce prefixes mirrored topics us-east.vaultcommerce.orders.placed.v1 in EU cluster. replication.factor matches target cluster policy.

Key points

  • MirrorMaker 2 — Kafka Connect based cross-cluster replication
  • Offset sync — checkpoint topic maps source/target offsets
  • Topic rename — sourceAlias.targetTopic convention
  • Replication lag — cross-region network bound; alert on MM2 lag
  • Active-passive DR — secondary cluster warm standby

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Failover planning
  • VaultCommerce rollout checklist

Test yourself

Answer these before moving on — recall is what makes it stick.