I’d like to jump into this task, first let me check the source :)
> On 7 Aug 2018, at 5:37 PM, Willem Jiang <[email protected]> wrote: > > Yeah, it's quit easy if we can leverage the current Pack framework. > I just create some sub tasks below SCB-665[1]. Please feel free to jump in > if you want to help :) > > [1]https://issues.apache.org/jira/browse/SCB-665 > > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Aug 6, 2018 at 9:47 PM, cherrylzhao <[email protected]> wrote: > >> That’s a great job ~ >> >> It seems to be satisfied our requirement very well. >> Omega and Alpha can be integrated with TCC, it looks like: >> 1. Begin transaction，alpha generate txid >> 2. Main service invoke try method of sub service. >> omega would register confirm and cancel method to alpha binding >> with txid. >> 3. Do commit/rollback >> this would trigger alpha to determine whether executing confirm or >> cancel >> >> >>> On 6 Aug 2018, at 5:11 PM, Zheng Feng <[email protected]> wrote: >>> >>> It is great. I will take a look. >>> >>> Willem Jiang <[email protected]> 于 2018年8月6日周一 11:58写道： >>> >>>> FYI, I just updated the design document[1] of Pack with TCC. >>>> >>>> Please feel free to add your comments here. >>>> >>>> [1] >>>> >>>> https://github.com/apache/incubator-servicecomb-saga/ >> blob/master/docs/design.md#workflow-tcc >>>> >>>> >>>> Willem Jiang >>>> >>>> Twitter: willemjiang >>>> Weibo: 姜宁willem >>>> >>>> On Sun, Aug 5, 2018 at 10:30 AM, cherrylzhao <[email protected]> wrote: >>>> >>>>> Hi, Willem >>>>> >>>>> Thanks for your quickly reply. >>>>> That’s a great idea for defining new TCC protocol ！ >>>>> >>>>> Best Wishes & Regards >>>>> >>>>>> On 4 Aug 2018, at 10:49 PM, Willem Jiang <[email protected]> >>>> wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> Current Pack (Omega/Alpha) supports to define the custom coordination >>>>>> protocol, >>>>>> So we can define a new TCC protocol instead of extends the old saga >>>>>> protocol. >>>>>> >>>>>> I'm post the TCC design proposal shortly in this weekend. >>>>>> >>>>>> >>>>>> Willem Jiang >>>>>> >>>>>> Twitter: willemjiang >>>>>> Weibo: 姜宁willem >>>>>> >>>>>> On Sat, Aug 4, 2018 at 5:44 PM, cherrylzhao <[email protected]> >> wrote: >>>>>> >>>>>>> Hi, all >>>>>>> >>>>>>> Currently, service comb saga transaction-manager have implemented >>>>>>> “confirm” and “cancel” process based on micro-service. >>>>>>> Due to saga model have’t ensure resource isolation，it need to deal >>>> with >>>>>>> the concurrent problem in business application. >>>>>>> We want to discuss whether it is possible to add a try interface >>>> within >>>>>>> service comb saga transaction manager. >>>>>>> Within “try” interface, users can lock resource before “confirm” >>>> process >>>>>>> execution. >>>>>>> >>>>>>> >>>>>>> Best Wishes & Regards >>>>>>> >>>>>>> >>>>> >>>>> >>>> >> >>
