Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 6da3a63 2fdb8fd)
Merge "Reuse current musicrangeinformation row if possible"
authorThomas Nelson <nelson24@att.com>
Mon, 15 Apr 2019 18:06:47 +0000 (18:06 +0000)
committerGerrit Code Review <gerrit@onap.org>
Mon, 15 Apr 2019 18:06:47 +0000 (18:06 +0000)
commitf4152e22bbf9bcde4996ad7a153ace4af99c5f0c
tree6ffb04fc37d2c3088d4f1a39cc643c01a77e88eatree | snapshot
parent6da3a637d010f0f8d1f06959d39ad91a95ef6c40commit | diff
parent2fdb8fdb419540fee28f8f98a04001979a45f70ecommit | diff
Merge "Reuse current musicrangeinformation row if possible"
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.