Are you using EventMesh? #290

vongosling · 2021-04-20T02:58:55Z

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

The text was updated successfully, but these errors were encountered:

vongosling · 2021-04-20T03:02:09Z

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.

qqeasonchen · 2021-04-20T03:16:35Z

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.

jinrongluo · 2021-09-14T15:19:27Z

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.

zscomehuyue · 2022-01-06T05:18:54Z

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.

ruanwenjun · 2022-01-18T06:37:43Z

Organization: Individual
Location: Shanghai
Contact: [email protected]
Version: v1.3.0
usage scenario: Study event driver architecture.

liwenzheng · 2022-01-18T06:38:14Z

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

mytang0 · 2022-09-23T11:49:15Z

Organization: 政采云
Location: Hangzhou, Zhejiang
Contact: [email protected]
Version: v1.6.0
usage scenario: Task scheduling for process orchestration.

UniKrau · 2022-11-13T22:11:29Z

Organization:ANZ Bank
Location: Melbourne, Australia
Contact: [email protected]
Version: NA
Usage scenarios: Unify PubSub messages with Cloud events spec, and personal learning

fengyongshe · 2022-11-14T09:13:59Z

Organization: China Mobile (Suzhou)software Technology Co.Ltd
Location: Suzhou, China
Contact: [email protected]
Version: NA
Usage scenarios: Event infrastructure in cloud computing

walterlife · 2022-11-14T09:15:05Z

Organization:Tencent
Location: Shenzhen, China
Contact: [email protected]
Version: NA
Usage scenarios: Serverless Workflow And FaaS

li-xiao-shuang · 2022-11-14T09:15:28Z

Organization: DIDI
Location: Beijing
Contact: [email protected]
Version: v1.6.0
usage scenario: Personal study of event-driven application architecture.

pchengma · 2022-11-14T09:16:24Z

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".

VNBear · 2022-11-14T09:20:07Z

Organization: 政采云
Location: Hangzhou, Zhejiang
Contact: [email protected]
Version: v1.6.0
usage scenario: Task scheduling for process orchestration.

horoc · 2022-11-14T09:28:21Z

Organization: Shopee
Location: Shanghai
Contact: [email protected]
Version: v1.6.0
usage scenario: Self-study of the event-driven component.

LIU-WEI-git · 2022-11-14T09:28:49Z

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.

mroccyen · 2022-11-14T09:38:27Z

Organization: biaoguoworks
Location: Chengdu
Contact: [email protected]
Version: v1.6.0
Usage scenario: Self-study of the event-driven component.

RiemannChow · 2022-11-14T13:20:22Z

Organization: Narwal
Location: Shenzhen, China
Contact: [email protected]
Version: NA
Usage scenarios: Serverless Workflow And FaaS

Markliniubility · 2022-11-15T02:25:10Z

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.

yangsq1 · 2022-11-28T11:46:33Z

Organization: navimentum
Location: BeiJing
Contact: [email protected]
Version: v1.4.0
usage scenario: Understanding Learning。

weihubeats · 2022-11-30T12:01:49Z

Organization: cider
Location: GuangZhou
Contact: [email protected]
Version: NA
usage scenario: Self-study of the event-driven component.

yelbom · 2023-04-10T00:57:12Z

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.

HattoriHenzo · 2023-07-25T12:28:10Z

Organization: Individual
Location: Québec, Canada
Contact: [email protected]
Version: N/A
Usage Scenario: Contribution and learning

harshithasudhakar · 2023-07-25T16:59:11Z

Organization: VIT University(Sophomore)
Location: Tamil Nadu, India
Contact: [email protected]
Version: NA
Usage Scenario: Contribute and learn ;)

black-snow · 2024-06-28T13:53:58Z

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.

vongosling pinned this issue Apr 20, 2021

vongosling added the discussion This issue requires further discussion label Apr 20, 2021

vongosling changed the title ~~Due Diligence for EventMesh~~ Are you using EventMesh Jun 8, 2021

vongosling changed the title ~~Are you using EventMesh~~ Are you using EventMesh? Jun 8, 2021

Pil0tXia added the pinned label Jan 10, 2024

Pil0tXia mentioned this issue Jan 19, 2024

Wanted: who's using EventMesh #8

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Are you using EventMesh? #290

Are you using EventMesh? #290

vongosling commented Apr 20, 2021 •

edited

Loading

vongosling commented Apr 20, 2021

qqeasonchen commented Apr 20, 2021 •

edited

Loading

jinrongluo commented Sep 14, 2021

zscomehuyue commented Jan 6, 2022 •

edited

Loading

ruanwenjun commented Jan 18, 2022

liwenzheng commented Jan 18, 2022

mytang0 commented Sep 23, 2022

UniKrau commented Nov 13, 2022

fengyongshe commented Nov 14, 2022

walterlife commented Nov 14, 2022 •

edited

Loading

li-xiao-shuang commented Nov 14, 2022

pchengma commented Nov 14, 2022 •

edited

Loading

VNBear commented Nov 14, 2022

horoc commented Nov 14, 2022 •

edited

Loading

LIU-WEI-git commented Nov 14, 2022 •

edited

Loading

mroccyen commented Nov 14, 2022 •

edited

Loading

RiemannChow commented Nov 14, 2022

Markliniubility commented Nov 15, 2022

yangsq1 commented Nov 28, 2022 •

edited

Loading

weihubeats commented Nov 30, 2022 •

edited

Loading

yelbom commented Apr 10, 2023

HattoriHenzo commented Jul 25, 2023

harshithasudhakar commented Jul 25, 2023

black-snow commented Jun 28, 2024 •

edited

Loading

Are you using EventMesh? #290

Are you using EventMesh? #290

Comments

vongosling commented Apr 20, 2021 • edited Loading

Due Diligence

What we expect from you

聆听你的声音

我们期待您能提供

vongosling commented Apr 20, 2021

qqeasonchen commented Apr 20, 2021 • edited Loading

jinrongluo commented Sep 14, 2021

zscomehuyue commented Jan 6, 2022 • edited Loading

ruanwenjun commented Jan 18, 2022

liwenzheng commented Jan 18, 2022

mytang0 commented Sep 23, 2022

UniKrau commented Nov 13, 2022

fengyongshe commented Nov 14, 2022

walterlife commented Nov 14, 2022 • edited Loading

li-xiao-shuang commented Nov 14, 2022

pchengma commented Nov 14, 2022 • edited Loading

VNBear commented Nov 14, 2022

horoc commented Nov 14, 2022 • edited Loading

LIU-WEI-git commented Nov 14, 2022 • edited Loading

mroccyen commented Nov 14, 2022 • edited Loading

RiemannChow commented Nov 14, 2022

Markliniubility commented Nov 15, 2022

yangsq1 commented Nov 28, 2022 • edited Loading

weihubeats commented Nov 30, 2022 • edited Loading

yelbom commented Apr 10, 2023

HattoriHenzo commented Jul 25, 2023

harshithasudhakar commented Jul 25, 2023

black-snow commented Jun 28, 2024 • edited Loading

vongosling commented Apr 20, 2021 •

edited

Loading

qqeasonchen commented Apr 20, 2021 •

edited

Loading

zscomehuyue commented Jan 6, 2022 •

edited

Loading

walterlife commented Nov 14, 2022 •

edited

Loading

pchengma commented Nov 14, 2022 •

edited

Loading

horoc commented Nov 14, 2022 •

edited

Loading

LIU-WEI-git commented Nov 14, 2022 •

edited

Loading

mroccyen commented Nov 14, 2022 •

edited

Loading

yangsq1 commented Nov 28, 2022 •

edited

Loading

weihubeats commented Nov 30, 2022 •

edited

Loading

black-snow commented Jun 28, 2024 •

edited

Loading