Replay Transaction Updates - music/mdbc - The most crucial recipe is a multi-site database cache (mdbc) that enable ONAP components that maintain state in a SQL database to avail the benefits of MUSIC without compromising their need to use transactional SQL DBs. These ONAP components can rely on existing db clustering techniques like MariaDB for transactionality and complex querying within a site. mdbc will intercept each of these read/write calls to the db cluster and mirror this state to other geo-distributed sites through MUSIC either synchronously or asynchronously (configurable at a table-level). For example, components like the ONAP Service Orchestrator that use MariaDB to maintain state can directly use this recipe with no change to their SQL code.

diff options

author	Tschaen, Brendan <ctschaen@att.com>	2019-08-06 13:37:29 -0400
committer	Tschaen, Brendan <ctschaen@att.com>	2019-08-06 13:40:06 -0400
commit	42214c84ef398fb65db4d84012de1e46c585f300 (patch)
tree	09c70ff4ff9d1064ce040220bd2d37adf2a4f902 /version.properties
parent	a98c068aa9a97b73aa1423f432674485a05bdb60 (diff)

Replay Transaction Updates

Simplify replay logic, already applied datastructure Remove table from txdigest column Issue-ID: MUSIC-421 Signed-off-by: Tschaen, Brendan <ctschaen@att.com> Change-Id: Ic757e6302e05d188704e625c76a77b106e000152

Diffstat (limited to 'version.properties')

0 files changed, 0 insertions, 0 deletions


context:
space:
mode: