Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: a98c068) | patch
Update MUSIC version 00/92300/2
authorTschaen, Brendan <ctschaen@att.com>
Tue, 30 Jul 2019 17:11:20 +0000 (13:11 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 30 Jul 2019 17:47:03 +0000 (13:47 -0400)
commit5431ea399fe0a31de79d493bc1748989a95c76d6
tree5d3e2baf1463651846ac22a184f0f4e6c0e41c93tree | snapshot
parenta98c068aa9a97b73aa1423f432674485a05bdb60commit | diff
Update MUSIC version

Issue-ID: MUSIC-466
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
Change-Id: I702b03282f12b02cc59942828a153e1f13cfc620
pom.xml diff | blob | history
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.