Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 9e21ff9) | patch
Use blob type in translog 28/90328/1
authorTschaen, Brendan <ctschaen@att.com>
Fri, 21 Jun 2019 19:26:17 +0000 (15:26 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Fri, 21 Jun 2019 19:26:17 +0000 (15:26 -0400)
commit13441563620ba912e79a71858da64aacb103ce0d
tree6beafd7714817c4f5cdeed764fe1612f6e453932tree | snapshot
parent9e21ff943f11df4c274b29989f5058c8054a9b39commit | diff
Use blob type in translog

Issue-ID: MUSIC-389
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
Change-Id: I970ee2111cf07e9246bed61676d6fd50009a6135
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.