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 service invocation #490

Closed
qqeasonchen opened this issue Aug 9, 2021 · 3 comments · Fixed by #508
Closed

[Feature] Support service invocation #490

qqeasonchen opened this issue Aug 9, 2021 · 3 comments · Fixed by #508
Labels
Milestone

Comments

@qqeasonchen
Copy link
Contributor

Feature Request

Currently EventMesh only support pub/sub, it would be wonderful if support request-reply like RPC.

Is your feature request related to a problem? Please describe

Describe the solution you'd like

Describe alternatives you've considered

Additional context

@liwenzheng
Copy link

我打算使用eventmesh作为业务系统的基础架构,不再引入service mesh之流,固需要RR能力。去年RocketMq推出了新功能Request Reply,所以在EventMesh中添加这个功能应该不难吧。希望能尽快加上去,应该对其他模块也不会有影响。

@qqeasonchen
Copy link
Contributor Author

@liwenzheng ok, let us do it together

@liwenzheng
Copy link

@qqeasonchen Thank you very much. Please speed up your time. I hope to test this month

xwm1992 added a commit that referenced this issue Aug 24, 2021
xwm1992 added a commit that referenced this issue Aug 25, 2021
* [ISSUE #490]Support service invocation

* remove unused code
@xwm1992 xwm1992 added this to the 1.3.0 milestone Dec 16, 2021
@xwm1992 xwm1992 changed the title Support service invocation [Feature] Support service invocation Dec 16, 2021
xwm1992 added a commit to xwm1992/EventMesh that referenced this issue Dec 27, 2021
* [ISSUE apache#490]Support service invocation

* remove unused code
xwm1992 added a commit that referenced this issue Aug 4, 2022
* [ISSUE #490]Support service invocation

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

Successfully merging a pull request may close this issue.

3 participants