The following important tasks are required before the 0.5.0 release 1. Support for Akka-based Alpha clusters SCB-1368[1] 2. Save the terminated transaction data to the database or es SCB-1369[2] 3. Support for query transaction data based on RESTful API SCB-1371 [3] 4. Implement one of the Alpha Event Channel Plugin SCB-1374 [4]
[1] https://issues.apache.org/jira/browse/SCB-1368 <https://issues.apache.org/jira/browse/SCB-1368> [2] https://issues.apache.org/jira/browse/SCB-1369 <https://issues.apache.org/jira/browse/SCB-1369> [3] https://issues.apache.org/jira/browse/SCB-1371 <https://issues.apache.org/jira/browse/SCB-1371> [4] https://issues.apache.org/jira/browse/SCB-1374 <https://issues.apache.org/jira/browse/SCB-1374> > 在 2019年7月17日，上午10:49，Willem Jiang <willem.ji...@gmail.com> 写道： > > big +1 on it. > > I think we need to let the user know about this change, as this state > machine part is in experimental status, I'm proposing that we list > the features which we want do in this release cycle at the end of this > August to make sure we can provide a basic runnable Saga coordinator > on top of state machine solution. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, Jul 17, 2019 at 10:26 AM Zhang Lei <zhang_...@boco.com.cn> wrote: >> >> Hi, all >> >> After reimplementing Saga with a state machine, we no longer need to perform >> complex table scans, so we can use ElasticSearch to persist transaction >> data. And use the ElasticSearch RESTful API to provide external query >> capabilities for terminating transactions. >> >> 1. Improve the performance of Alpha data persistence >> 2. This will reduce the performance impact of the query on Alpha >> 3. Users extend their monitoring capabilities based on ElasticSearch rich >> RESTful API >> >> Lei Zhang
