You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eventmesh.apache.org by GitBox <gi...@apache.org> on 2022/01/24 06:22:36 UTC

[GitHub] [incubator-eventmesh] liwenzheng opened a new issue #740: [Feature] The data flow is changed from synchronous to asynchronous

liwenzheng opened a new issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740


   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
   
   
   ### Feature Request
   
   Hi ,all. At present, sending messages adopts multi-threaded synchronous processing. This is done to implement the pub / sub model. However, doing so will lead to the coupling of the client to the mesh. The flow of messages should not depend on some implementation method, but on the message itself. If you agree with this approach, I think the following improvements can be made:
   
   1. Add attributes to the agreement, such as source and destination.
   
   2. Add a memory queue to store messages.
   
   3. Improve TCP connect to cooperate with message flow.
   ![image](https://user-images.githubusercontent.com/1767832/150732045-0fa4d7ae-95a8-4360-834c-6c436ef96a7e.png)
   
   what do you think about it ?
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019914280


   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only pro
 vide various types of transportation tools, and should not care about what to send.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng commented on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916302


   
   
   
   > 
   
   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only pro
 vide various types of transportation tools, and should not care about what to send.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   @qqeasonchen 
   ok,I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only provide various types of transportation tools, and should not care about what to send or where to send,but next node.  
   ```
   我认为在Event-Mesh生态中，Mesh集群就好比一家物流公司，Event则是货物，将货物送到哪里，
   是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，
   由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，
   而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥以及送到哪里，只关注下一个节点在哪儿。
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only pro
 vide various types of transportation tools, and should not care about what to send.  @qqeasonchen 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng closed issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng closed issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng commented on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only pro
 vide various types of transportation tools, and should not care about what to send.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] qqeasonchen commented on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
qqeasonchen commented on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019860747


   @liwenzheng glad to see this, we can have a discussion.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng removed a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng removed a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019914280


   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only pro
 vide various types of transportation tools, and should not care about what to send.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   @qqeasonchen 
   ok,I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only provide various types of transportation tools, and should not care about what to send.  
   ```
   我认为在Event-Mesh生态中，Mesh集群就好比一家物流公司，Event则是货物，将货物送到哪里，
   是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，
   由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，
   而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥以及送到哪里，只关注下一个节点在哪儿。
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   @qqeasonchen   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client no
 de can only provide various types of transportation tools, and should not care about what to send.  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   @qqeasonchen 
   ok,I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only provide various types of transportation tools, and should not care about what to send.  
   ```
   我认为在Event-Mesh生态中，Mesh集群就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng commented on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng commented on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019914280


   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] github-actions[bot] commented on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019759958


   Welcome to the Apache EventMesh (incubating) community!!
   We are glad that you are contributing by opening this issue. :D
   
   Please make sure to include all the relevant context.
   We will be here shortly.
   
   If you are interested in contributing to our project, please let us know!
   You can check out our contributing guide on [contributing to EventMesh](https://github.com/apache/incubator-eventmesh/blob/develop/CONTRIBUTING.md).
   
   Want to get closer to the community?
   
   WeChat Group：
   ![wechat_qr](https://github.com/apache/incubator-eventmesh/blob/develop/docs/images/mesh-helper.png?raw=true)
   
   Mailing Lists:
   | Name | Description |Subscribe	|Unsubscribe|Archive
   | ----    | ----    |----    | ----    | ----    |
   |Users	|User support and questions mailing list|	[Subscribe](mailto:users-subscribe@eventmesh.incubator.apache.org)	|[Unsubscribe](mailto:users-unsubscribe@eventmesh.incubator.apache.org)	|[Mail Archives](https://lists.apache.org/list.html?users@eventmesh.apache.org)|
   |Development	|Development related discussions|	[Subscribe](mailto:dev-subscribe@eventmesh.incubator.apache.org)	|[Unsubscribe](mailto:dev-unsubscribe@eventmesh.incubator.apache.org)	|[Mail Archives](https://lists.apache.org/list.html?dev@eventmesh.apache.org)|
   |Commits	|All commits to repositories|	[Subscribe](mailto:commits-subscribe@eventmesh.incubator.apache.org)	|[Unsubscribe](mailto:commits-unsubscribe@eventmesh.incubator.apache.org)	|[Mail Archives](https://lists.apache.org/list.html?commits@eventmesh.apache.org)|


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   @qqeasonchen 
   ok,I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only provide various types of transportation tools, and should not care about what to send.  
   ```
   我认为在Event-Mesh生态中，Mesh集群就好比一家物流公司，Event则是货物，将货物送到哪里，
   是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，
   由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，
   而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng edited a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng edited a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916588


   @qqeasonchen   ok,我认为在Event-Mesh生态中，Mesh集群就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / cli
 ent node can only provide various types of transportation tools, and should not care about what to send.  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org

[GitHub] [incubator-eventmesh] liwenzheng removed a comment on issue #740: [Feature] The data flow is changed from synchronous to asynchronous

Posted by GitBox <gi...@apache.org>.
liwenzheng removed a comment on issue #740:
URL: https://github.com/apache/incubator-eventmesh/issues/740#issuecomment-1019916302


   
   
   
   > 
   
   ok,我认为在Event-Mesh生态中，Mesh就好比一家物流公司，Event则是货物，将货物送到哪里，是由货物自身的订单决定。整个行程可以分为很多段，每一段由两个驿站组成，而驿站之间的送货方式，由他们自己决定。每一种送货方式 都不应该跨过驿站。说这么多，无非是想说，Event货物 决定路线，而Mesh/Client节点则只能提供多种类型的运送工具，而不应该关心送的啥。I think in the event mesh ecosystem, mesh is like a logistics company. Event is goods. Where the goods are sent is determined by the orders of the goods themselves. The whole journey can be divided into many sections. Each section is composed of two post stations, and the delivery method between the post stations is decided by themselves. Each delivery method should not cross the post station. By saying so much, I just want to say that event goods determine the route, while the mesh / client node can only pro
 vide various types of transportation tools, and should not care about what to send.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org