Re: [DISCUSSION] About Pack module refactoring

[Willem Jiang]

I don't like the flatten modules,
it will add some maintance trouble for us if we introduce the flatten modules.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Feb 24, 2022 at 5:20 PM Lei Zhang  wrote:
>
> Can we take a small step first? Just rename modules and flatten them.
>
> Current modules:
>
> acceptance-tests
> alpha
> demo
> docker-build-config
> docs
> distribution
> integration-tests
> omega
> pack-common
> pack-contracts
> persistence
> web
>
> Refactored modules:
>
> docker(docker-build-config)
> pack-docs(docs)
> pack-common-core(pack-common)
> pack-common-contracts-grpc(pack-contracts/pack-contract-grpc)
> pack-alpha-benchmark(alpha/alpha-benchmark)
> pack-alpha-server-common(alpha/alpha-core)
> pack-alpha-server-fsm(alpha/alpha-fsm)
> pack-alpha-server(alpha/alpha-server)
> pack-alpha-server-cloud-starter-consul(alpha/alpha-spring-cloud-starter-consul)
> pack-alpha-server-cloud-starter-eureka(alpha/alpha-spring-cloud-starter-eureka)
> pack-alpha-server-cloud-starter-nacos(alpha/alpha-spring-cloud-starter-nacos)
> pack-alpha-server-persistence-jpa(persistence/persistence-jpa)
> pack-alpha-ui(alpha-ui)
> pack-tests-acceptance(acceptance-tests)
> pack-tests-integration(integration-tests)
> pack-examples(pack-demo)
> pack-distribution(distribution)
> pack-omega(omega)
> pack-omega-transaction(omega-transaction)
> pack-omega-context(omega-context)
> pack-omega-spring-tx(omega-spring-tx)
> pack-omega-transport(omega-transport)
> pack-omega-connector(omega-connector)
> pack-omega-spring-starter(omega-spring-starter)
> pack-omega-spring-cloud-eureka-starter(omega-spring-cloud-eureka-starter)
> pack-omega-spring-cloud-consul-starter(omega-spring-cloud-consul-starter)
> pack-omega-spring-cloud-zookeeper-starter(omega-spring-cloud-zookeeper-starter)
> pack-omega-spring-cloud-nacos-starter(omega-spring-cloud-nacos-starter)
> pack-omega-format(omega-format)
> web(deprecate?)
>
> Zheng Feng  于2021年3月24日周三 23:48写道：
>
> > +1 and I also want to extract some SPI interfaces for alpha-server and
> > these can help users to implement some other saga pattern in the future.
> > I add the LRA in my todo list since the spec will be released 1.0 Final
> > very soon.
> >
> > Willem Jiang  于2021年3月22日周一 上午8:59写道：
> >
> > > +1.  We should seperate the implementations of Saga and TCC, when
> > > starting the alpha server, users should be able to configure the
> > > modules as they want.
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sat, Mar 20, 2021 at 1:29 PM Lei Zhang  wrote:
> > > >
> > > > Hi, Park Team
> > > >
> > > > Currently, Park's module division is unclear, difficult for
> > contributors
> > > to
> > > > participate.
> > > >
> > > > I suggest dividing the modules again and use SPI to provide these
> > > > components.
> > > >
> > > > The operations can be quite involved, requiring many steps to complete
> > > the
> > > > reconstruction. I think we can start with the division of modules for
> > > > example:
> > > >
> > > > * state machine mode does not require DB,
> > > > * state machine mode persistence layer should be easily replaced
> > > > * non-state machine mode Saga and TCC Should be split into two modules,
> > > etc.
> > > >
> > > > This is just my initial thoughts, any suggestions？
> > > >
> > > > alpha-benchmark
> > > > alpha-server-ui
> > > > alpha-server-core
> > > > alpha-server-saga-db
> > > > alpha-server-saga-fsm
> > > > alpha-server-tcc-db
> > > > alpha-server-tcc-fsm (maybe)
> > > > alpha-server-bootstrap (I expect that only this module depends on the
> > > > framework infrastructure in the future)
> > > > alpha-server-discovery-plugin-consul
> > > > alpha-server-discovery-plugin-eureka
> > > > alpha-server-discovery-plugin-nacos
> > > > alpha-server-discovery-plugin-zookeeper
> > > >
> > > > Best regards,
> > > > Lei Zhang
> > >
> >

Re: [DISCUSSION] About Pack module refactoring

[Lei Zhang]

Can we take a small step first? Just rename modules and flatten them.

Current modules:

acceptance-tests
alpha
demo
docker-build-config
docs
distribution
integration-tests
omega
pack-common
pack-contracts
persistence
web

Refactored modules:

docker(docker-build-config)
pack-docs(docs)
pack-common-core(pack-common)
pack-common-contracts-grpc(pack-contracts/pack-contract-grpc)
pack-alpha-benchmark(alpha/alpha-benchmark)
pack-alpha-server-common(alpha/alpha-core)
pack-alpha-server-fsm(alpha/alpha-fsm)
pack-alpha-server(alpha/alpha-server)
pack-alpha-server-cloud-starter-consul(alpha/alpha-spring-cloud-starter-consul)
pack-alpha-server-cloud-starter-eureka(alpha/alpha-spring-cloud-starter-eureka)
pack-alpha-server-cloud-starter-nacos(alpha/alpha-spring-cloud-starter-nacos)
pack-alpha-server-persistence-jpa(persistence/persistence-jpa)
pack-alpha-ui(alpha-ui)
pack-tests-acceptance(acceptance-tests)
pack-tests-integration(integration-tests)
pack-examples(pack-demo)
pack-distribution(distribution)
pack-omega(omega)
pack-omega-transaction(omega-transaction)
pack-omega-context(omega-context)
pack-omega-spring-tx(omega-spring-tx)
pack-omega-transport(omega-transport)
pack-omega-connector(omega-connector)
pack-omega-spring-starter(omega-spring-starter)
pack-omega-spring-cloud-eureka-starter(omega-spring-cloud-eureka-starter)
pack-omega-spring-cloud-consul-starter(omega-spring-cloud-consul-starter)
pack-omega-spring-cloud-zookeeper-starter(omega-spring-cloud-zookeeper-starter)
pack-omega-spring-cloud-nacos-starter(omega-spring-cloud-nacos-starter)
pack-omega-format(omega-format)
web(deprecate?)

Zheng Feng  于2021年3月24日周三 23:48写道：

> +1 and I also want to extract some SPI interfaces for alpha-server and
> these can help users to implement some other saga pattern in the future.
> I add the LRA in my todo list since the spec will be released 1.0 Final
> very soon.
>
> Willem Jiang  于2021年3月22日周一 上午8:59写道：
>
> > +1.  We should seperate the implementations of Saga and TCC, when
> > starting the alpha server, users should be able to configure the
> > modules as they want.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Mar 20, 2021 at 1:29 PM Lei Zhang  wrote:
> > >
> > > Hi, Park Team
> > >
> > > Currently, Park's module division is unclear, difficult for
> contributors
> > to
> > > participate.
> > >
> > > I suggest dividing the modules again and use SPI to provide these
> > > components.
> > >
> > > The operations can be quite involved, requiring many steps to complete
> > the
> > > reconstruction. I think we can start with the division of modules for
> > > example:
> > >
> > > * state machine mode does not require DB,
> > > * state machine mode persistence layer should be easily replaced
> > > * non-state machine mode Saga and TCC Should be split into two modules,
> > etc.
> > >
> > > This is just my initial thoughts, any suggestions？
> > >
> > > alpha-benchmark
> > > alpha-server-ui
> > > alpha-server-core
> > > alpha-server-saga-db
> > > alpha-server-saga-fsm
> > > alpha-server-tcc-db
> > > alpha-server-tcc-fsm (maybe)
> > > alpha-server-bootstrap (I expect that only this module depends on the
> > > framework infrastructure in the future)
> > > alpha-server-discovery-plugin-consul
> > > alpha-server-discovery-plugin-eureka
> > > alpha-server-discovery-plugin-nacos
> > > alpha-server-discovery-plugin-zookeeper
> > >
> > > Best regards,
> > > Lei Zhang
> >
>

Re: [DISCUSSION] About Pack module refactoring

[Zheng Feng]

+1 and I also want to extract some SPI interfaces for alpha-server and
these can help users to implement some other saga pattern in the future.
I add the LRA in my todo list since the spec will be released 1.0 Final
very soon.

Willem Jiang  于2021年3月22日周一 上午8:59写道：

> +1.  We should seperate the implementations of Saga and TCC, when
> starting the alpha server, users should be able to configure the
> modules as they want.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Mar 20, 2021 at 1:29 PM Lei Zhang  wrote:
> >
> > Hi, Park Team
> >
> > Currently, Park's module division is unclear, difficult for contributors
> to
> > participate.
> >
> > I suggest dividing the modules again and use SPI to provide these
> > components.
> >
> > The operations can be quite involved, requiring many steps to complete
> the
> > reconstruction. I think we can start with the division of modules for
> > example:
> >
> > * state machine mode does not require DB,
> > * state machine mode persistence layer should be easily replaced
> > * non-state machine mode Saga and TCC Should be split into two modules,
> etc.
> >
> > This is just my initial thoughts, any suggestions？
> >
> > alpha-benchmark
> > alpha-server-ui
> > alpha-server-core
> > alpha-server-saga-db
> > alpha-server-saga-fsm
> > alpha-server-tcc-db
> > alpha-server-tcc-fsm (maybe)
> > alpha-server-bootstrap (I expect that only this module depends on the
> > framework infrastructure in the future)
> > alpha-server-discovery-plugin-consul
> > alpha-server-discovery-plugin-eureka
> > alpha-server-discovery-plugin-nacos
> > alpha-server-discovery-plugin-zookeeper
> >
> > Best regards,
> > Lei Zhang
>

Re: [DISCUSSION] About Pack module refactoring

[Willem Jiang]

+1.  We should seperate the implementations of Saga and TCC, when
starting the alpha server, users should be able to configure the
modules as they want.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Mar 20, 2021 at 1:29 PM Lei Zhang  wrote:
>
> Hi, Park Team
>
> Currently, Park's module division is unclear, difficult for contributors to
> participate.
>
> I suggest dividing the modules again and use SPI to provide these
> components.
>
> The operations can be quite involved, requiring many steps to complete the
> reconstruction. I think we can start with the division of modules for
> example:
>
> * state machine mode does not require DB,
> * state machine mode persistence layer should be easily replaced
> * non-state machine mode Saga and TCC Should be split into two modules, etc.
>
> This is just my initial thoughts, any suggestions？
>
> alpha-benchmark
> alpha-server-ui
> alpha-server-core
> alpha-server-saga-db
> alpha-server-saga-fsm
> alpha-server-tcc-db
> alpha-server-tcc-fsm (maybe)
> alpha-server-bootstrap (I expect that only this module depends on the
> framework infrastructure in the future)
> alpha-server-discovery-plugin-consul
> alpha-server-discovery-plugin-eureka
> alpha-server-discovery-plugin-nacos
> alpha-server-discovery-plugin-zookeeper
>
> Best regards,
> Lei Zhang

[DISCUSSION] About Pack module refactoring

[Lei Zhang]

Hi, Park Team

Currently, Park's module division is unclear, difficult for contributors to
participate.

I suggest dividing the modules again and use SPI to provide these
components.

The operations can be quite involved, requiring many steps to complete the
reconstruction. I think we can start with the division of modules for
example:

* state machine mode does not require DB,
* state machine mode persistence layer should be easily replaced
* non-state machine mode Saga and TCC Should be split into two modules, etc.

This is just my initial thoughts, any suggestions？

alpha-benchmark
alpha-server-ui
alpha-server-core
alpha-server-saga-db
alpha-server-saga-fsm
alpha-server-tcc-db
alpha-server-tcc-fsm (maybe)
alpha-server-bootstrap (I expect that only this module depends on the
framework infrastructure in the future)
alpha-server-discovery-plugin-consul
alpha-server-discovery-plugin-eureka
alpha-server-discovery-plugin-nacos
alpha-server-discovery-plugin-zookeeper

Best regards,
Lei Zhang