Are you using EventMesh?
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
## Due Diligence
EventMesh is a dynamic cloud-native eventing infrastruture used to decouple the application and backend middleware layer, which supports a wide range of use cases that encompass complex multi-cloud, widely distributed topologies using diverse technology stacks. In order to better understand the use of the EventMesh and continue to optimize it. Here, we sincerely invite you to take a minute to feedback on your usage scenario.
## What we expect from you
Pls. submit a comment in this issue to include the following information:
• your company, school or organization
• your country and city
• your contact info, such as email, WeChat and twitter (optional).
• usage scenario
• expectations(optional)
You can refer to the following sample answer for the format:
```
* Organization: XX Company
* Location: Silicon Valley, USA
* Contact: messi10@gmail.org
* Version: v1.1.0
* Usage scenario: Event Processing framework, support sidecar, and center deployment...
* Expectations(optional): Serverless backend infra
```
Thanks again for your participation!
Apache EventMesh Community
## 聆听你的声音
EventMesh是一个动态云原生事件基础架构,用于解耦应用程序和后端中间件层,它支持广泛的使用情形,包括使用不同技术堆栈的复杂多云、广泛分布的拓扑。为了更好地理解EventMesh的使用并继续优化它。在这里,我们真诚地邀请您花一分钟时间反馈您的使用场景。
### 我们期待您能提供
一条评论, 评论内容包括但不限于:
• 您所在公司、学校或组织
• 您所在的国家与城市
• 您的联系方式: 邮箱、微信、Twitter账号 (为了更好地保持联系,建议您留下联系方式)
• 您将Apache EventMesh 用于哪些业务场景,使用规模如何
• 您对Apache EventMesh 未来发展有什么期望?
您可以参考下面的样例来提供您的信息:
```
* 公司:XX有限公司
* 地点:美国硅谷
* 联系方式:messi10@gmail.com
* 版本: v1.1.0
* 场景与规模:实时通讯系统,主要用于实时消息通道、用户上下线事件通知、消息送达通知等核心场景,目前服务端大约200+台broker,客户端规模5000+台 4core 16g 虚拟机。
* 期望(可选):支持更多标准,如OpenSchema
```
非常感谢您的参与
Apache EventMesh Community
Contributor guide
Research direction
Review the issue's requested response fields and sample format. No files, tests, or entry points are mentioned; the work is complete when a comment documents the user's organization, location, optional contact details, usage scenario, version, and expectations.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100