From dev-return-6056-archive-asf-public=cust-asf.ponee.io@servicecomb.apache.org Fri Apr 26 10:41:06 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 96EE918064C for ; Fri, 26 Apr 2019 12:41:06 +0200 (CEST) Received: (qmail 53032 invoked by uid 500); 26 Apr 2019 10:41:06 -0000 Mailing-List: contact dev-help@servicecomb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@servicecomb.apache.org Delivered-To: mailing list dev@servicecomb.apache.org Received: (qmail 53014 invoked by uid 99); 26 Apr 2019 10:41:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2019 10:41:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D431DC285C for ; Fri, 26 Apr 2019 10:41:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.049 X-Spam-Level: ** X-Spam-Status: No, score=2.049 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=126.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id AUXmx7q0Rm4X for ; Fri, 26 Apr 2019 10:41:02 +0000 (UTC) Received: from m50-111.126.com (m50-111.126.com [123.125.50.111]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F35B860DE4 for ; Fri, 26 Apr 2019 10:41:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=126.com; s=s110527; h=From:Mime-Version:Subject:Message-Id:Date; bh=8w1jQ xwy0aCfST7tEhNbI+zQMMD7hIUqFd2a13ZR6bQ=; b=ArcAskrXz/xxCLfj0xgII k5j/va9tmSSDrQT8DO25yfUo8LWcwYlXXbes9pa3XtznnT/BXXYAmvDCWgKooGMw g5q8QE1Qhym3x/6q8LtVCFYSQYnnmqztpY3zbyjgFSjJ8uEQ1w11yzPVQvwN0SdQ CuMihf1o/XTlF19nQqa1Es= Received: from [10.13.116.74] (unknown [111.200.23.43]) by smtp5 (Coremail) with SMTP id jtKowACnuaTs38JcThQYAw--.1366S3; Fri, 26 Apr 2019 18:40:53 +0800 (CST) From: zhaojun Content-Type: multipart/alternative; boundary="Apple-Mail=_A4960747-8ED4-470E-BEE6-CC7A7DA3D268" Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: [saga-actuator]consider about adding StreamBasedSaga engine to integrate with shardingsphere Message-Id: <48B56C10-8A83-4E13-9767-26AF7E9DC173@126.com> Date: Fri, 26 Apr 2019 18:39:38 +0800 Cc: dev@shardingsphere.apache.org To: "dev@servicecomb.apache.org" X-Mailer: Apple Mail (2.3445.100.39) X-CM-TRANSID:jtKowACnuaTs38JcThQYAw--.1366S3 X-Coremail-Antispam: 1Uf129KBjvdXoWrur1kKFyrZFW3uw4DJr1DWrg_yoWDWrX_uF Z7K3W7JwsxZF18tw1YkF4YgrZ7ua1j9ry7Ar1Yyw4q934xAan8Zr4DWrs5ZrnxX3ySq3yY krZ2kw47AwnFvjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IU03PE7UUUUU== X-Originating-IP: [111.200.23.43] X-CM-SenderInfo: p2kd0ypxqyjqqrswhudrp/1tbiFhaiMFpD9JLt0QAAsR --Apple-Mail=_A4960747-8ED4-470E-BEE6-CC7A7DA3D268 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, all currently, we have integrated with saga using graph based engine in = shardingsphere[1] it need us to collect all participated actual SQL, then submit to saga = actuator in commit/rollback phase. if application crashed before invoking saga actuator, undo log of branch = transaction SQL will not be saved,=20 so recovery thread will not be executed correctly. it's better that encapsulating every actual SQL as a saga task in = shardingsphere side,=20 then submit to saga actuator realtime instead of batch processing all = the SQLs at commit/rollback phase.=20 this architecture will make the boundary more clear between = shardingsphre and saga, currently we have done some additional works for = integrating saga. any thought? = [1]:https://github.com/sharding-sphere/shardingsphere-spi-impl/tree/master= /sharding-transaction-spi-impl/sharding-transaction-base-spi-impl/sharding= -transaction-base-saga = ------------------ Zhao Jun Apache Sharding-Sphere & ServiceComb --Apple-Mail=_A4960747-8ED4-470E-BEE6-CC7A7DA3D268--