Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 45ffc11 b4e66e8)
Merge "Remove ownership logic from mixin"
authorBharath Balasubramanian <bharathb@research.att.com>
Tue, 12 Mar 2019 23:24:52 +0000 (23:24 +0000)
committerGerrit Code Review <gerrit@onap.org>
Tue, 12 Mar 2019 23:24:52 +0000 (23:24 +0000)
commitf61985dedb975a777bed88fb17c482d0dbb73cd8
treee6026e3c8d75468a2c5227401ce2a9560a34d8fbtree | snapshot
parent45ffc11e5cecf8112032d9d67c9c652f4836eacdcommit | diff
parentb4e66e8087274a656b1301ecb55fee4af183bf36commit | diff
Merge "Remove ownership logic from mixin"
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.