Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 66e0e40 a290a03)
Merge "Warm up ranges across sites"
authorBharath Balasubramanian <bharathb@research.att.com>
Mon, 25 Mar 2019 23:11:59 +0000 (23:11 +0000)
committerGerrit Code Review <gerrit@onap.org>
Mon, 25 Mar 2019 23:11:59 +0000 (23:11 +0000)
commita40ee886c28bc28db1794792f1fb312b723d48fb
tree10a6ee7cc31694d4815df2ea22512d357fbee00atree | snapshot
parent66e0e407c48d2288ce0d7d6f8129487a29de8c02commit | diff
parenta290a037ea6da2dc062945f77240a10564f6541fcommit | diff
Merge "Warm up ranges across sites"
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/DBInterface.java diff1 | diff2 | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MySQLMixin.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.