Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 1359bbd) | patch
Use MariaDB libraries 07/78707/1
authorTschaen, Brendan <ctschaen@att.com>
Mon, 18 Feb 2019 21:31:30 +0000 (16:31 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Mon, 18 Feb 2019 21:34:02 +0000 (16:34 -0500)
commit0de9c4556d917999a851ed0b7d063bdf99d588f2
tree0688870453921fd2bdcb2c437ee4da4def315ba8tree | snapshot
parent1359bbd68acb27e47e32b5dff8b7f35354584366commit | diff
Use MariaDB libraries

Change-Id: I240b94f7381c45b548b8d70714a4fcdb383a14aa
Issue-ID: MUSIC-337
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-benchmark/pom.xml diff | blob | history
mdbc-server/pom.xml diff | blob | history
pom.xml 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.