Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 019a55a) | patch
Fix Eventual consistency 58/78158/2
authorst782s <statta@research.att.com>
Fri, 8 Feb 2019 22:30:33 +0000 (17:30 -0500)
committerSunder Tattavarada <statta@research.att.com>
Mon, 11 Feb 2019 12:10:06 +0000 (12:10 +0000)
commit1359bbd68acb27e47e32b5dff8b7f35354584366
treea2d21eb08bad1572cd692c80fe51db6efb1e817etree | snapshot
parent019a55afae68f555348d60cc197b0d188eaaf4afcommit | diff
Fix Eventual consistency

Issue-ID: MUSIC-319
Change-Id: I7433e7d71c44ffe623e560863e7e1fd9c0f247ce
Signed-off-by: st782s <statta@research.att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/examples/MdbcTestClient.java [changed mode: 0755->0644] diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicMixin.java diff | blob | history
mdbc-server/src/main/resources/music.properties 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.