Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 14d46d9 5431ea3)
Merge "Update MUSIC version"
authorBharath Balasubramanian <bharathb@research.att.com>
Mon, 12 Aug 2019 19:03:56 +0000 (19:03 +0000)
committerGerrit Code Review <gerrit@onap.org>
Mon, 12 Aug 2019 19:03:56 +0000 (19:03 +0000)
commit84c322b7d05bb820af38421fbda75e8dc9817c69
tree38fa2146c798edfb87dc9a3d2a60f399496fe56dtree | snapshot
parent14d46d99cb31f20da0bcfbdd559703cb97bf0baacommit | diff
parent5431ea399fe0a31de79d493bc1748989a95c76d6commit | diff
Merge "Update MUSIC version"
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.