Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: ba7c4ff) | patch
Clean up ownership work 47/74347/2
authorTschaen, Brendan <ctschaen@att.com>
Thu, 6 Dec 2018 17:23:54 +0000 (12:23 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Fri, 7 Dec 2018 15:54:01 +0000 (10:54 -0500)
commit60f81b9378283965503992cad44b6073d77251b5
tree6a3a3ad1deb1bdae6a3086f9b1e09ffe9fb6a7eatree | snapshot
parentba7c4ffe49495ad0e2ce986192f65c8ae63bb2bdcommit | diff
Clean up ownership work

leverage DatabasePartition class
remove extra classes, improve workflow
remove failing unit test
ensure example runs all the way through

Change-Id: If8d59d207d093d4245b9d6cb5bd59c7fe1ebfb19
Issue-ID: MUSIC-230
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/DatabasePartition.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/MdbcServerLogic.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/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/query/QueryProcessor.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
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.