I think the core implementation of TCC and Saga (Pack) have the same
things, such as the similar annotations and the event names. So does it
make sense to  have the common core module to implement the transaction
context, transaction event and the grpc communication protocol ?
And we could provide the different APIs or annotations for both the TCC and
the Saga or maybe the other  distribute transaction protocol. Also we could
make a new roadmap to make it as a framework used in the microservice to
resolve the transaction things.

Anyway, I totally agree with Willem to separate the TCC and the Saga codes
at the first step. And what is the next ? Maybe we need a new name for the
repo ?

Regards,
Zheng Feng

Willem Jiang <willem.ji...@gmail.com> 于2018年10月23日周二 下午2:54写道:

> Hi Team,
>
> As TCC is quite different with the Saga implementation.
> I'm planning to move the Pack code and TCC related code out of Saga repo.
> In this way we can just keep Saga repo to have the implementation for Saga.
>
> Any thought?
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Aug 29, 2018 at 5:27 PM Willem Jiang <willem.ji...@gmail.com>
> wrote:
> >
> > Yeah, once we plan to support the TCC in the Saga project , we need to
> consider to rename the project name.
> > Current we have two different implementation of Saga,  one is centric
> Saga, the other is based the Pack (Omega/Alpha).
> > Now we implement the TCC protocol on top of Pack architecture.
> >
> > Maybe we can rearrange the package name base on this Architecture and
> move the Pack code to another repo.
> > Any thought?
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> >
> > On Wed, Aug 29, 2018 at 5:09 PM fu chengeng <oliug...@hotmail.com>
> wrote:
> >>
> >> Hi all.
> >>     as we all knows that,saga is a kind of transaction agreement,And we
> named this project as saga because we support only this kind of agreement.
> >>     But now,we are going to support tcc, and maybe many other
> transaction agreement like xa will be supported.
> >>     Whether we should change saga to other name to prevent confused
> when it is in incubating?
> >>
> >>
>

Reply via email to