Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 1344156) | patch
Relinquish Locks aptly based on partition 04/90404/2
authorstatta <statta@research.att.com>
Mon, 24 Jun 2019 16:27:38 +0000 (12:27 -0400)
committerst782s <statta@research.att.com>
Mon, 24 Jun 2019 21:16:12 +0000 (17:16 -0400)
commitf947968a2c417dac743ea40046ee5ad12dd6bd6f
tree9ef40a2cc31e83065ad4859f8af41dbfa09bc839tree | snapshot
parent13441563620ba912e79a71858da64aacb103ce0dcommit | diff
Relinquish Locks aptly based on partition

Issue-ID: MUSIC-402
Change-Id: I9b54939920521b13649253794d82789b46727acd
Signed-off-by: statta <statta@research.att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcConnection.java diff | blob | history
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
mdbc-server/src/main/java/org/onap/music/mdbc/query/QueryProcessor.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.