kparisa opened a new issue, #3764:
URL: https://github.com/apache/iggy/issues/3764
### Description
**Summary**
Implement an Iggy Source Connector that consumes data from an upstream Iggy
cluster and publishes it into a downstream Iggy cluster.
This enables seamless cluster-to-cluster replication and provides the
foundation for multi-region deployments, disaster recovery, active-active
architectures, edge-to-cloud streaming, and hierarchical streaming topologies.
Unlike traditional application-level replication, this connector allows
operators to replicate selected streams, partitions, or namespaces without
requiring producers or consumers to change.
**Motivation**
Many production deployments require data to exist in multiple locations.
Today, applications would need to publish to multiple Iggy clusters
directly, increasing complexity and coupling replication logic into business
applications.
A native Iggy Source Connector would make replication a first-class
capability by continuously consuming from one cluster and publishing to another
while preserving ordering and delivery guarantees.
Producers
│
▼
+------------------+
| Iggy Cluster A |
| (Primary) |
+------------------+
│
Iggy Source Connector
│
▼
+------------------+
| Iggy Cluster B |
| (Replica) |
+------------------+
│
Local Consumers
The connector should behave like any other Iggy connector:
* Source = upstream Iggy
* Sink = downstream Iggy
### Affected area / component
Connectors
### Proposed solution
_No response_
### Alternatives considered
_No response_
### Contribution
- [ ] I'm willing to submit a pull request to implement this feature
### Good first issue
- [x] I think this could be a good first issue for a new contributor
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
