Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: f947968 2ed3e00)
Merge "Keep history of MRI rows in table"
authorThomas Nelson <nelson24@att.com>
Tue, 25 Jun 2019 20:17:08 +0000 (20:17 +0000)
committerGerrit Code Review <gerrit@onap.org>
Tue, 25 Jun 2019 20:17:08 +0000 (20:17 +0000)
commitdcdded9d153295c176053c245772a67eef222aa8
tree2139f9537d984cb629138d97a41c23ab8404b036tree | snapshot
parentf947968a2c417dac743ea40046ee5ad12dd6bd6fcommit | diff
parent2ed3e003a73db9970e0942a2466cd27e29c08f63commit | diff
Merge "Keep history of MRI rows in table"
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicInterface.java diff1 | diff2 | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicMixin.java diff1 | diff2 | blob | history
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.