TxDigest replay and code restructure - 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>	2018-11-16 10:05:50 -0500
committer	Tschaen, Brendan <ctschaen@att.com>	2018-11-16 15:48:20 -0500
commit	5a7cf00e87cacf97130d3f1823adce824f865c69 (patch)
tree	31e93f6bb7e45c2c17974340762675a1c57a55e0 /docs/uml.svg
parent	cacb64c5ed4f2c67965aba7d44148c61568dc2bc (diff)

TxDigest replay and code restructure

Spin off replay daemon in its own object Create musictxdaemon test Fix licensing issue MusicRow Info has database partition object Change-Id: I22117f8e9309fb5d8bc99ec35d4145e655f4e5a2 Issue-ID: MUSIC-166 Signed-off-by: Tschaen, Brendan <ctschaen@att.com>

Diffstat (limited to 'docs/uml.svg')

0 files changed, 0 insertions, 0 deletions


context:
space:
mode: