Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 97fe11b) | patch
Don't create extra locks while claiming ownership 97/88897/2
authorArthur Martella <arthur.martella.1@att.com>
Thu, 30 May 2019 13:46:02 +0000 (09:46 -0400)
committerArthur Martella <arthur.martella.1@att.com>
Thu, 30 May 2019 14:17:25 +0000 (10:17 -0400)
commit65b45cafb4dff93bef52e91f2ab3f2a772e4472e
tree5e5406bf1dcd89ad60633606b38c20b05b960c13tree | snapshot
parent97fe11b3e90ead341cecae5365340962c3896deacommit | diff
Don't create extra locks while claiming ownership

Issue-ID: MUSIC-402
Signed-off-by: Martella, Arthur <arthur.martella.1@att.com>
Change-Id: I12b9ff80be0429ff7a9fc68074a3ca2ec133aee2
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.