You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
Reacted by Wenjun, Pengcheng Ma (Enoch) and firgavin
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: jin.rong.luo@huawei.com
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: zscomehuyue@126.com
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.
Reacted by zscomehuyue, Eason Chen, mike_xwm, Wenjun, Heng Du and vongosling
Organization:ANZ Bank
Location: Melbourne, Australia
Contact: unikrau@gmail.com
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: fengyongshe@139.com
Version: NA
Usage scenarios: Event infrastructure in cloud computing
Organization: The Chinese University of Hong Kong
Location: Hong Kong
Contact: pchengma@link.cuhk.edu.hk
Version: v1.5.0
Usage scenario: Google Summer of Code'2022 Contributor to "Apache EventMesh Support Knative as Eventing Infra".
Organization: School of Computer Science, Northwestern Polytechnical University
Location: Xi'an, China
Contact: timcross-wei@qq.com
Version: NA
Usage scenarios: Learning cloud-native and event-driven architecture.
Organization: University of California, Los Angeles
Location: Los Angeles, US
Contact: limarksmail@gmail.com
Version: NA
usage scenario: learn about event driver architecture and pub/sub messages with Cloud events spec.
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.
Reacted by yelbom, Eason Chen and Harshitha Sudhakar
Organization: VIT University(Sophomore)
Location: Tamil Nadu, India
Contact: harshithasudhakar1710@gmail.com
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.
Activity
vongosling commentedon Apr 20, 2021
qqeasonchen commentedon Apr 20, 2021
[-]Due Diligence for EventMesh[/-][+]Are you using EventMesh[/+][-]Are you using EventMesh[/-][+]Are you using EventMesh?[/+]jinrongluo commentedon Sep 14, 2021
Organization: Huawei
Location: Shenzhen, Guangdong
Contact: jin.rong.luo@huawei.com
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.
zscomehuyue commentedon Jan 6, 2022
Organization: 永辉彩食鲜
Location: Beijing
Contact: zscomehuyue@126.com
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.
ruanwenjun commentedon Jan 18, 2022
Organization: Individual
Location: Shanghai
Contact: bestruanwenjun@gmail.com
Version: v1.3.0
usage scenario: Study event driver architecture.
liwenzheng commentedon Jan 18, 2022
Organization:FORMS SYNTRON
Location: Shenzhen, Guangdong
Contact: liwenzheng.love@163.com
Version: v1.2.0
usage scenario: as a cloud native architecture, message broker,and personal learning
mytang0 commentedon Sep 23, 2022
Organization: 政采云
Location: Hangzhou, Zhejiang
Contact: mengyang.t@163.com
Version: v1.6.0
usage scenario: Task scheduling for process orchestration.
UniKrau commentedon Nov 13, 2022
Organization:ANZ Bank
Location: Melbourne, Australia
Contact: unikrau@gmail.com
Version: NA
Usage scenarios: Unify PubSub messages with Cloud events spec, and personal learning
fengyongshe commentedon Nov 14, 2022
Organization: China Mobile (Suzhou)software Technology Co.Ltd
Location: Suzhou, China
Contact: fengyongshe@139.com
Version: NA
Usage scenarios: Event infrastructure in cloud computing
walterlife commentedon Nov 14, 2022
Organization:Tencent
Location: Shenzhen, China
Contact: walterzywei@gmail.com
Version: NA
Usage scenarios: Serverless Workflow And FaaS
li-xiao-shuang commentedon Nov 14, 2022
Organization: DIDI
Location: Beijing
Contact: lixiaoshuang@apache.org
Version: v1.6.0
usage scenario: Personal study of event-driven application architecture.
pchengma commentedon Nov 14, 2022
Organization: The Chinese University of Hong Kong
Location: Hong Kong
Contact: pchengma@link.cuhk.edu.hk
Version: v1.5.0
Usage scenario: Google Summer of Code'2022 Contributor to "Apache EventMesh Support Knative as Eventing Infra".
VNBear commentedon Nov 14, 2022
Organization: 政采云
Location: Hangzhou, Zhejiang
Contact: 791029369@qq.com
Version: v1.6.0
usage scenario: Task scheduling for process orchestration.
horoc commentedon Nov 14, 2022
Organization: Shopee
Location: Shanghai
Contact: horoc.chen@gmail.com
Version: v1.6.0
usage scenario: Self-study of the event-driven component.
LIU-WEI-git commentedon Nov 14, 2022
Organization: School of Computer Science, Northwestern Polytechnical University
Location: Xi'an, China
Contact: timcross-wei@qq.com
Version: NA
Usage scenarios: Learning cloud-native and event-driven architecture.
mroccyen commentedon Nov 14, 2022
Organization: biaoguoworks
Location: Chengdu
Contact: qingshanpeng@126.com
Version: v1.6.0
Usage scenario: Self-study of the event-driven component.
RiemannChow commentedon Nov 14, 2022
Organization: Narwal
Location: Shenzhen, China
Contact: riemannchowcn@gmail.com
Version: NA
Usage scenarios: Serverless Workflow And FaaS
Markliniubility commentedon Nov 15, 2022
Organization: University of California, Los Angeles
Location: Los Angeles, US
Contact: limarksmail@gmail.com
Version: NA
usage scenario: learn about event driver architecture and pub/sub messages with Cloud events spec.
yangsq1 commentedon Nov 28, 2022
Organization: navimentum
Location: BeiJing
Contact: yangsq1@139.com
Version: v1.4.0
usage scenario: Understanding Learning。
weihubeats commentedon Nov 30, 2022
Organization: cider
Location: GuangZhou
Contact: weihubeats@139.com
Version: NA
usage scenario: Self-study of the event-driven component.
yelbom commentedon Apr 10, 2023
HattoriHenzo commentedon Jul 25, 2023
Organization: Individual
Location: Québec, Canada
Contact: reachmeongithub@yahoo.com
Version: N/A
Usage Scenario: Contribution and learning
harshithasudhakar commentedon Jul 25, 2023
Organization: VIT University(Sophomore)
Location: Tamil Nadu, India
Contact: harshithasudhakar1710@gmail.com
Version: NA
Usage Scenario: Contribute and learn ;)
black-snow commentedon Jun 28, 2024
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.