Omega and Alpha can still use Grpc to talk to each other. We just reimplement the Alpha internal logic with Akka State machine. Current we won't change the protocol between Omega and Alpha.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Jun 19, 2019 at 2:35 PM zhaojun <zhaoju...@126.com> wrote: > > Hi, Zhang Lei, > > If we use AKKA, how can we design the actors, and how can we guarantee omega > will receive the message synchronize. > > Best Regards > ------------------ > Zhao Jun > Apache Sharding-Sphere & ServiceComb > > > > On Jun 19, 2019, at 11:42 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > > > > Hi Zhang Lei, > > > > It's great to hear from you for the proposal. Do you mind share us > > more detail about the alpha-fsm module? > > If you can show us some design document and prototype PR, then we > > could discuss more detail about the implementation. > > > > Maybe we work from the design document first, please feel free to > > update the wiki page with your questions. > > > > Regards， > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Jun 19, 2019 at 10:07 AM Zhang Lei <zhang_...@boco.com.cn> wrote: > >> > >> We plan to use the state machine to track transaction status in the wiki > >> [1]. I think we can create a state machine prototype and test it by > >> creating a new alpha-fsm module in alpha. > >> I have completed the basic prototype and test cases of the state machine > >> based on AKKA. I want to share with you through this module to discuss my > >> views on this aspect. Secondly, we perfect the existing function and add > >> new functions in the module. > >> > >> Need to be further explored and verified by practice: > >> 1. Akka Persistence and Recover > >> 2. High availability with Akka Cluster > >> 3. Message Broker & State Machine > >> > >> [1]https://cwiki.apache.org/confluence/display/SERVICECOMB/Using+StateMachine+for+tracing+the+transaction+states >
