Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: b357ddb) | patch
Switch to using mariadb connector 58/77658/1
authorTschaen, Brendan <ctschaen@att.com>
Thu, 31 Jan 2019 16:02:41 +0000 (11:02 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 31 Jan 2019 16:02:41 +0000 (11:02 -0500)
commitc260a14f888e09ce767ac6b9f6353c87f0cd034d
treecfb64491e75952539e8c9eb3b6800ddbc6228da4tree | snapshot
parentb357ddb0869c2cc44eb0bd5800ed66914f49c468commit | diff
Switch to using mariadb connector

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