Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 6f363a8) | patch
Insert/update interchange and PS issue 84/82984/2
authorstatta <statta@research.att.com>
Thu, 21 Mar 2019 21:57:57 +0000 (17:57 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Fri, 22 Mar 2019 15:07:17 +0000 (11:07 -0400)
commit66e0e407c48d2288ce0d7d6f8129487a29de8c02
tree94555aadfdbc71c8574bbc509634ab0cb4f7e386tree | snapshot
parent6f363a89863a91ac104e5c77f0096636a8db5343commit | diff
Insert/update interchange and PS issue

Issue-ID: MUSIC-276
Change-Id: I9c9b990cb362adae81e621db527a0f890e00c7eb
Signed-off-by: statta <statta@research.att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcPreparedStatement.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/DBInterface.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/mixins/MySQLMixin.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.