Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: d2b5c18 40397fc)
Merge "Dependency missing in nexus"
authorBrendan Tschaen <ctschaen@att.com>
Tue, 10 Sep 2019 16:55:14 +0000 (16:55 +0000)
committerGerrit Code Review <gerrit@onap.org>
Tue, 10 Sep 2019 16:55:14 +0000 (16:55 +0000)
commita05dc5ddab778a0305402c8d1ecb6297e9fbd9aa
tree55d7c28450dd1de07d72463275af3a7ebb513482tree | snapshot
parentd2b5c18e008c4be333ff0f5c47d1d8136802f6b6commit | diff
parent40397fcdea9f3dc782032c9d2162dca9c05431adcommit | diff
Merge "Dependency missing in nexus"
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.