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 09:55:15 UTC

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

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