Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 77212c2) | patch
Remove ownership logic from mixin 42/79742/1
authorTschaen, Brendan <ctschaen@att.com>
Tue, 5 Mar 2019 22:46:20 +0000 (17:46 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 5 Mar 2019 22:46:20 +0000 (17:46 -0500)
commitb4e66e8087274a656b1301ecb55fee4af183bf36
treec0281edeeaf8a95ff4e55a314634dd659ebc8151tree | snapshot
parent77212c23b8ec060c3b15ab21c33502b1bd24e858commit | diff
Remove ownership logic from mixin

Change-Id: I70d62e76e23c690726294c62b9222c4cd9659c70
Issue-ID: MUSIC-326
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
12 files changed:
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcConnection.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/StateManager.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/LockRequest.java [new file with mode: 0644] blob
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/LockResult.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MixinFactory.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/Music2Mixin.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/tables/MusicTxDigest.java diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/mixins/MusicMixinTest.java diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/ownership/OwnershipAndCheckpointTest.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.