[Feature] Enhance the serverless ability of EventMesh

[xwm1992]

Search before asking

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

Feature Request

EventMesh currently has Eventing capabilities in the serverless field, but it should also improve and supplement the automatic expansion and contraction capabilities of eventmesh's own services and access services. This service is the coordinator responsible for automatically scaling services connected to EventMesh, supporting automatic scaling from 0 to n and scaling down from n to 0 based on event traffic or other user conditions.

Implement the auto scaling service for eventmesh, which can support different auto scaling strategies by default, or knative and keda can be selected as plugin services for automatic expansion and contraction of the service.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct *

[HarshSawarkar]

Hi @xwm1992 I have previous contribution experience in EventMesh and would love to work on this issue under GSOC24. Can you please guide?

[harshithasudhakar]

Hi @xwm1992, I have been actively contributing and closely following the project's development and would also like to have the opportunity to work on issues in GSOC 24' under your guidance. Would you please guide me through the further steps?

[hanshal101]

Hi @xwm1992 This issue looks interesting to me. I'll be participating in GSOC'24. I have extensive experience in DevOps engineering. Can you please share more information on this issue.

[qqeasonchen]

@Alonexc please update the design docs here, thank you.

[qqeasonchen]

https://functionmesh.io/
https://github.com/streamnative/function-mesh

[Pil0tXia]

Everyone can contact the community with any ideas you have, and the tutor will help you to refine the detailed design of this subject.

[github-actions]

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.