Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: ed4b4af) | patch
Read write lock implementation 87/88187/3
authorTschaen, Brendan <ctschaen@att.com>
Tue, 21 May 2019 17:19:40 +0000 (13:19 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Wed, 22 May 2019 19:29:58 +0000 (15:29 -0400)
commit92a80130ba924dc7b101b978bdad1d0fba14b141
tree5bee5c732a20600c82a497b1463641a69b135559tree | snapshot
parented4b4af2de4b02efd3f097323e9a999f905e60e6commit | diff
Read write lock implementation

Change-Id: Ifd680da39305adf36e8a4946643a17e9e0a4df97
Issue-ID: MUSIC-326
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/MDBCUtils.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcConnection.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ProxyStatement.java [deleted file] blob | history
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/LockRequest.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/test/java/org/onap/music/mdbc/mixins/MusicMixinTest.java diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/mixins/MySQLMixinTest.java [moved from mdbc-server/src/test/java/org/onap/music/mdbc/MySQLMixinTest.java with 96% similarity] 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.