Home / Companies / Redpanda / Blog / Post Details
Content Deep Dive

Me and my shadow (link!): Disaster recovery replication made easy

Blog post from Redpanda

Post Details
Company
Date Published
Author
Paul Wilkinson
Word Count
2,238
Company Posts That Month
7
Language
English
Hacker News Points
-
Post removed?
No
Summary

Redpanda introduces Shadow Linking, a built-in feature for enterprise-grade disaster recovery, which simplifies the replication of streaming data for business continuity. This feature allows data to be replicated to another cluster with perfect fidelity, ensuring minimal disruption during outages by reducing Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs). Shadow Linking operates on a simple active-passive architecture, where a source cluster handles all production traffic while a shadow cluster remains read-only until a failover is necessary. This broker-native solution offers advantages over traditional tools like Apache MirrorMaker 2.0 by providing seamless data consistency, reduced operational complexity, and efficient infrastructure utilization without requiring additional hardware. By enabling asynchronous replication, Shadow Linking ensures that messages maintain the same offsets, facilitating easier failovers and eliminating the risk of message duplication. Additionally, it supports reciprocal active-passive architectures, allowing organizations to distribute risk across multiple regions while maintaining low-latency data access. The feature is designed for easy integration and management, with Prometheus-compatible metrics and multiple configuration options, making it a robust tool for ensuring data resilience and operational efficiency in streaming environments.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 4 6,296 1,346 246 -2%
Kubernetes 2 2,306 381 103 +25%
AI Agents 1 4,430 1,100 236 -3%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.