Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 0325143 c8a7c3a)
Merge "Adding to current partition, and releaseLock bug"
authorThomas Nelson <nelson24@att.com>
Tue, 2 Apr 2019 22:29:35 +0000 (22:29 +0000)
committerGerrit Code Review <gerrit@onap.org>
Tue, 2 Apr 2019 22:29:35 +0000 (22:29 +0000)
commit8703beababa99e3cf7c66995f28cf254de54616d
treecb986816c496444d6abf3163bf49a7dbc2f0ec8btree | snapshot
parent0325143a8ddc6e95a5d02517468b3c8de40da9b5commit | diff
parentc8a7c3a0e11e80e365c5a0e7c2a12f87315dc61ccommit | diff
Merge "Adding to current partition, and releaseLock bug"
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.