Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Support federated connector #577

Closed
1 of 2 tasks
qqeasonchen opened this issue Oct 31, 2021 · 1 comment
Closed
1 of 2 tasks

[Feature] Support federated connector #577

qqeasonchen opened this issue Oct 31, 2021 · 1 comment
Labels

Comments

@qqeasonchen
Copy link
Contributor

qqeasonchen commented Oct 31, 2021

Search before asking

  • I had searched in the issues and found no similar issues.

Feature Request

Currently, A event routes to eventstore when publish to EventMesh, and consumes by another EventMesh from eventstore, but if a event can route from one eventmesh to another eventmesh, eventstore will not must be shared between eventmesh of publisher and subscriber at the same time.
That means a event can route from one eventmesh to another one dynamically, and they are full mesh among eventmeshes.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
@qqeasonchen qqeasonchen changed the title [Feature] Enabling bridge between EventMeshs [Feature] Support federated connector Nov 1, 2021
@mroccyen
Copy link
Contributor

please assign to me, i will try my best to finish it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants