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