Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 8ee3c10 b7c20b1)
Merge "New test script for MDBC"
authorThomas Nelson <nelson24@att.com>
Mon, 8 Apr 2019 20:01:16 +0000 (20:01 +0000)
committerGerrit Code Review <gerrit@onap.org>
Mon, 8 Apr 2019 20:01:16 +0000 (20:01 +0000)
commit6da3a637d010f0f8d1f06959d39ad91a95ef6c40
treea6e72f41d0003acba9acdf558a5b9697a969d5ddtree | snapshot
parent8ee3c10928c025c3908ce60314c40dd22755e544commit | diff
parentb7c20b1b912f0e858bd55416ab35c9f93febce94commit | diff
Merge "New test script for 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.