Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 32dbfd3 394d23b)
Merge "End test with a select all"
authorThomas Nelson <nelson24@att.com>
Thu, 25 Jul 2019 20:17:25 +0000 (20:17 +0000)
committerGerrit Code Review <gerrit@onap.org>
Thu, 25 Jul 2019 20:17:25 +0000 (20:17 +0000)
commita98c068aa9a97b73aa1423f432674485a05bdb60
tree7816cc2e2c9fb303fc7961badca4eb3928071610tree | snapshot
parent32dbfd3759fc2aa20e8f03637b8fcc281c3730e2commit | diff
parent394d23b48b5baffe02230e47ff3479c913cf9b55commit | diff
Merge "End test with a select all"
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.