Keep replication fast and recovery independent
Brooklin Kafka replication moves streams between systems with strong multitenancy and partition-level controls. Independent backups preserve older recovery points when a current replica contains the same damaged data as its source.
What Brooklin Kafka replication does well
Brooklin is a distributed system for reliable nearline streaming across different source and destination systems. LinkedIn designed it for multitenant deployments with many independent data streams.
For Kafka mirroring, Brooklin supports regular expression topic selection and partition-level fault isolation. Its management API can pause or resume individual partitions. A diagnostics API reports stream status on demand.
OSO Kafka Backup stores Kafka records, consumer group offsets, and topic configuration outside the live cluster. It writes to S3, Azure Blob, GCS, or a filesystem. Restore can target another cluster and stop at a millisecond timestamp.
The tools address different recovery needs. Brooklin keeps another system current. Backup retains known-good history after a harmful event reaches every live replica. The disaster recovery guide maps both layers to specific failure modes.
| Feature | OSO Kafka Backup | LinkedIn Brooklin |
|---|---|---|
| Primary job | Backup and restore | Nearline data streaming and replication |
| Best fit | Historical recovery | Multitenant data movement |
| Kafka destination | Same or different Kafka cluster | Another Kafka cluster |
| Independent storage | Object storage or filesystem | Destination system |
| Point-in-time recovery | Yes | No |
| Older state after replicated errors | Retained for restore | Not a replication goal |
| Consumer group offset preservation | Built-in | Not an independent backup snapshot |
| Topic selection | Include and exclude patterns | Regular expression whitelist |
| Failure isolation | Partition processing | Partition-level stream isolation |
| Operations | CLI or Kubernetes operator | Management and diagnostics APIs |
| Extensibility | Kafka backup storage backends | Source and destination adapters |
| License | Open source (MIT) | Open source (BSD-2-Clause) |
When to choose Brooklin or backup
Choose Brooklin when you need a maintained platform for multitenant Kafka mirroring or data movement across heterogeneous systems. Its APIs and partition controls fit teams operating many concurrent streams.
Choose OSO Kafka Backup when you need independent recovery points, millisecond-precision restore, portable object storage, or preserved consumer group offsets.
Run both when fast failover and historical recovery matter. Brooklin can keep a target cluster current. Backup preserves an earlier state when the replicated state is unsafe. The alternatives guide explains this protection model in more detail.
Frequently asked questions
Is Brooklin a Kafka backup tool?
No. Brooklin moves data between source and destination systems, including Kafka clusters. It does not create independent, timestamped backups for historical restore.
What does Brooklin do well?
Brooklin supports multitenant streaming, partition-level fault isolation, regular expression topic selection, and management APIs for pausing or resuming individual partitions.
Is LinkedIn Brooklin still maintained?
Yes. The official project repository remains active and is not archived. Teams should still test each release against their Kafka versions and operating requirements.
Can Brooklin and OSO Kafka Backup run together?
Yes. Use Brooklin to maintain a current destination and OSO Kafka Backup for independently stored recovery points. Each protects against different failure modes.
Ready to protect your Kafka data?
Take your first backup in minutes with the open source CLI, or talk to us about Enterprise features like encryption, RBAC, and audit logging.