Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 885a7be) | patch
Refactorization of musicmixin's own code 26/79726/1
authorTschaen, Brendan <ctschaen@att.com>
Mon, 4 Mar 2019 20:49:00 +0000 (15:49 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 5 Mar 2019 17:52:39 +0000 (12:52 -0500)
commit77212c23b8ec060c3b15ab21c33502b1bd24e858
tree4d00d50c862f013dbb87121dd141fb1536e9f3a0tree | snapshot
parent885a7bea8709bece6244990cbeba9b1cccc40ddccommit | diff
Refactorization of musicmixin's own code

Issue-ID: MUSIC-326
Change-Id: Ia07ff8e6e5c6bd9444f8967eae392a67bf08b7f2
Signed-off-by: Tschaen, Brendan <ctschaen@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/MusicMixin.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ownership/Dag.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/MriRowComparator.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.