Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: bdec440 8b0ee17)
Merge "Music Tx Digest Decoding Script"
authorThomas Nelson <nelson24@att.com>
Wed, 26 Jun 2019 15:00:51 +0000 (15:00 +0000)
committerGerrit Code Review <gerrit@onap.org>
Wed, 26 Jun 2019 15:00:51 +0000 (15:00 +0000)
commit07ea54cfc9341cfc5cc64526e1d357981e6841ed
treea35fc31556a90420abefcc381ae02ee14c073a13tree | snapshot
parentbdec440ecc0854529c60659683cd3acd4696fd1ccommit | diff
parent8b0ee179cfcc2ea668f2a6c48197019bf7f0dcaccommit | diff
Merge "Music Tx Digest Decoding Script"
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.