Imteyaz, Let me try to answer your question. In your example, the order of the executions will not be guaranteed. The implementation of the service should guarantee it in no matter what the way is.
1) If the update address happens 2 times will they be executed in ordered > fasion (If it is async) > Depend on which call is received, put into the thread pool, and get executed first. > 2) If say if the first update stuck then second call not execute untill > first one not clear or gets executed. The second will not be stuck by the first unless the service implementation has synchronization. On Fri, Jan 18, 2019 at 11:49 PM Imteyaz Khan <[email protected]> wrote: > It was mine bad, I should have provided more details. I was looking for > information about how serialization of call or ordering against a call in > context of a key happen in dubbo. e.g. lets say I have a person service > with the capability of user address update, now this service get 2 call for > same user address update. > The information I am looking for how things will work in the below mention > case > > 1) If the update address happens 2 times will they be executed in ordered > fasion (If it is async) > 2) If say if the first update stuck then second call not execute untill > first one not clear or gets executed. > > Please do let me know, if I have failed to explained my above example > clearly. > > > > > On Fri, Jan 18, 2019 at 12:30 PM 田 小波 <[email protected]> wrote: > > > Hi, > > > > Hi All, > > Could someone point me to any doc or material or with any information > > which can help me to understand the ordering of invocation in dubbo and > how > > it works? > > > > This article[1] analyzes Dubbo's calling process in detail, but > > unfortunately, this article is only available in Chinese. > > For non-native Chinese speakers, please translate via Chrome or Google > > Translate. > > > > [1] > > > http://dubbo.apache.org/zh-cn/docs/source_code_guide/service-invoking-process.html > > > > Regards, > > Xiaobo > > > > >
