Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 9715bb3) | patch
Adding to current partition, and releaseLock bug 38/83638/3
authorTschaen, Brendan <ctschaen@att.com>
Thu, 28 Mar 2019 17:46:50 +0000 (13:46 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 28 Mar 2019 19:52:23 +0000 (15:52 -0400)
commitc8a7c3a0e11e80e365c5a0e7c2a12f87315dc61c
treec3e12413da36e2831097ba43255861101dd04425tree | snapshot
parent9715bb302ae309810fe533ad024cafe87e5480ddcommit | diff
Adding to current partition, and releaseLock bug

Change-Id: I9801656a32480c26b39dea5ae59fd27053d92f29
Issue-ID: MUSIC-374
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/examples/MdbcTestClient.java diff | blob | history
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/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.