eventmesh
eventmesh copied to clipboard
apache
Are you using EventMesh?
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: [email protected]
* 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有限公司
* 地点：美国硅谷
* 联系方式：[email protected]
* 版本： v1.1.0
* 场景与规模：实时通讯系统，主要用于实时消息通道、用户上下线事件通知、消息送达通知等核心场景，目前服务端大约200+台broker，客户端规模5000+台 4core 16g 虚拟机。
* 期望（可选）：支持更多标准，如OpenSchema
非常感谢您的参与 Apache EventMesh Community
- Organization: Google
- Location: Silicon Valley, USA
- Contact: [email protected]
- Version: v1.1.0
- usage scenario: Comparing with other mesh solutions, about realtime and stability to capable doing realtime notification, realtime streams, parallelism process over microservices and db replications.
- Organization: WeBank
- Location: Shenzhen, Guangdong
- Contact: [email protected]
- Version: v1.1.0
- usage scenario: Distributed financial-level message bus, used in massive financial transaction scenarios to facilitate the access of various language systems.
Organization: Huawei Location: Shenzhen, Guangdong Contact: [email protected] Version: v1.0.0 usage scenario: Managed cloud native central event bus and orchestration engine, used by thousands of event driven cloud services and applications in various industries.
Organization: 永辉彩食鲜 Location: Beijing Contact: [email protected] Version: v1.2.0 usage scenario: Managed cloud native central event bus and orchestration engine, used by thousands of event driven cloud services and applications in various industries.
Organization: Individual Location: Shanghai Contact: [email protected] Version: v1.3.0 usage scenario: Study event driver architecture.
Organization:FORMS SYNTRON Location: Shenzhen, Guangdong Contact: [email protected] Version: v1.2.0 usage scenario: as a cloud native architecture, message broker，and personal learning
Organization: 政采云 Location: Hangzhou, Zhejiang Contact: [email protected] Version: v1.6.0 usage scenario: Task scheduling for process orchestration.
Organization:ANZ Bank Location: Melbourne, Australia Contact: [email protected] Version: NA Usage scenarios: Unify PubSub messages with Cloud events spec, and personal learning
Organization: China Mobile (Suzhou)software Technology Co.Ltd Location: Suzhou, China Contact: [email protected] Version: NA Usage scenarios: Event infrastructure in cloud computing
Organization:Tencent Location: Shenzhen, China Contact: [email protected] Version: NA Usage scenarios: Serverless Workflow And FaaS
Organization: DIDI Location: Beijing Contact: [email protected] Version: v1.6.0 usage scenario: Personal study of event-driven application architecture.
Organization: The Chinese University of Hong Kong Location: Hong Kong Contact: [email protected] Version: v1.5.0 Usage scenario: Google Summer of Code'2022 Contributor to "Apache EventMesh Support Knative as Eventing Infra".
Organization: 政采云 Location: Hangzhou, Zhejiang Contact: [email protected] Version: v1.6.0 usage scenario: Task scheduling for process orchestration.
Organization: Shopee Location: Shanghai Contact: [email protected] Version: v1.6.0 usage scenario: Self-study of the event-driven component.
Organization: School of Computer Science, Northwestern Polytechnical University Location: Xi'an, China Contact: [email protected] Version: NA Usage scenarios: Learning cloud-native and event-driven architecture.
Organization: biaoguoworks Location: Chengdu Contact: [email protected] Version: v1.6.0 Usage scenario: Self-study of the event-driven component.
Organization: Narwal Location: Shenzhen, China Contact: [email protected] Version: NA Usage scenarios: Serverless Workflow And FaaS
Organization: University of California, Los Angeles Location: Los Angeles, US Contact: [email protected] Version: NA usage scenario: learn about event driver architecture and pub/sub messages with Cloud events spec.
Organization: navimentum Location: BeiJing Contact: [email protected] Version: v1.4.0 usage scenario: Understanding Learning。
Organization: cider Location: GuangZhou Contact: [email protected] Version: NA usage scenario: Self-study of the event-driven component.
- Organization: KLA & Google
- Location: Portland, Oregon
- Contact: [email protected]
- Version: na
- Usage scenario: very novice with software but have had an amazing time navigating all these apps. Excited to become proficient and be able to develop / collaborate.
- Expectations(optional): Just learn.
Organization: Individual Location: Québec, Canada Contact: [email protected] Version: N/A Usage Scenario: Contribution and learning
Organization: VIT University(Sophomore) Location: Tamil Nadu, India Contact: [email protected] Version: NA Usage Scenario: Contribute and learn ;)
Organization: - Location: Germany Contact: @mention me here Version: - Usage Scenario: Comparing with other solutions.
At the moment I'm wondering if EventMesh is a real thing. I see there's code and diagrams promising a lot of what I'd want, yet there's little documentation and I wouldn't really know how to use and operate this thing. So is anyone outside of WeBank actually using it? How? Did I just miss the actual documentation?
I've been building the EDA backbone mostly by hand in the last company and will probably do it again in this one. Featuring AsyncAPI, CloudEvents, a registry, several sinks and sources, EventMesh could be a quite good off-the-shelf alternativ. But online resources are scarce and even scarcer in English.
Another alternative I'm looking into is building atop of dapr.
