Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 77212c2 c521acf)
Merge "Include version.properties"
authorThomas Nelson <nelson24@att.com>
Fri, 8 Mar 2019 21:29:24 +0000 (21:29 +0000)
committerGerrit Code Review <gerrit@onap.org>
Fri, 8 Mar 2019 21:29:24 +0000 (21:29 +0000)
commit45ffc11e5cecf8112032d9d67c9c652f4836eacd
tree53df91ed622089f296019e77e7ff870e5736b4eatree | snapshot
parent77212c23b8ec060c3b15ab21c33502b1bd24e858commit | diff
parentc521acf91ac6c76bc83015102624ed141d69dbf0commit | diff
Merge "Include version.properties"
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.