Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 1f36e43 e2031a7)
Merge "Relinquish locks for each transaction"
authorThomas Nelson <nelson24@att.com>
Fri, 7 Jun 2019 18:38:04 +0000 (18:38 +0000)
committerGerrit Code Review <gerrit@onap.org>
Fri, 7 Jun 2019 18:38:04 +0000 (18:38 +0000)
commitd3e986759875605e43acabbb1283270440a1a1a7
tree7e177f585b06d4ecbf579f0da08c7c24df5c0cf1tree | snapshot
parent1f36e4303bf76b752eed9ebb8c79a80c31139037commit | diff
parente2031a7220812eec652354c3c705c81ef30b9deacommit | diff
Merge "Relinquish locks for each transaction"
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.