Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 9715bb3) | patch
Add primary key for delete in tx replay 42/83642/1
authorArthur Martella <arthur.martella.1@att.com>
Thu, 28 Mar 2019 18:00:03 +0000 (14:00 -0400)
committerArthur Martella <arthur.martella.1@att.com>
Thu, 28 Mar 2019 18:00:03 +0000 (14:00 -0400)
commit0325143a8ddc6e95a5d02517468b3c8de40da9b5
tree5f1b9d4df9b1c4e29b2a50e2a6dd6588c448ae91tree | snapshot
parent9715bb302ae309810fe533ad024cafe87e5480ddcommit | diff
Add primary key for delete in tx replay

Change-Id: Ic8a2e8c311dd657fbdb5936568bc8d168458d3b2
Issue-ID: MUSIC-371
Signed-off-by: Arthur Martella <arthur.martella.1@att.com>
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.