Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: a1c1b4b) | patch
Reuse current musicrangeinformation row if possible 72/84272/1
authorTschaen, Brendan <ctschaen@att.com>
Thu, 4 Apr 2019 20:18:51 +0000 (16:18 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 4 Apr 2019 20:18:51 +0000 (16:18 -0400)
commit2fdb8fdb419540fee28f8f98a04001979a45f70e
treef9a8ff0c3cb9f753c0987af634381782d5b3f6batree | snapshot
parenta1c1b4ba47e9c8ef1fa4e7b8a3ea8ab272050baecommit | diff
Reuse current musicrangeinformation row if possible

Change-Id: I748a43cefada08df42894968698adcf48a635afb
Issue-ID: MUSIC-326
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicInterface.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicMixin.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ownership/OwnershipAndCheckpoint.java diff | 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.