MirrorMaker 2 & Tiered Storage

Cross-region replication and S3-backed cold segments.

0/2 done

DR + cost

Two scaling moves

  • MirrorMaker 2 — Kafka-Connect-based replication across clusters. Handles topic renaming (source.topicName), ACL sync and offset translation so consumers can fail over between clusters without losing their place.
  • Tiered Storage (KIP-405) — keep hot segments on broker disks, offload cold ones to S3 / GCS / MinIO. Dramatic cost win for long-retention compliance topics.

Both are operational levers, not data-model decisions.

MirrorMaker 2 topic replication config

Replicate orders and payments from us-east-1 to eu-west-1 with offset translation enabled.

Reflect

Plan your DR posture.

  • Active-passive or active-active across regions?
  • Who owns failover runbooks — platform or each consumer team?

Reading in progress · 0 of 2 activities done