Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 60f81b9) | patch
Allow configurable database name 51/74451/2
authorTschaen, Brendan <ctschaen@att.com>
Mon, 10 Dec 2018 15:24:27 +0000 (10:24 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 13 Dec 2018 20:14:26 +0000 (15:14 -0500)
commitad9faf285c9348728859c49b0883bff82ec5031e
treeecb8d9553763c2853de610be029127f3004feee2tree | snapshot
parent60f81b9378283965503992cad44b6073d77251b5commit | diff
Allow configurable database name

Change-Id: I967df28f2f5281e7eee6a03087a279cbbe9f6e3e
Issue-ID: MUSIC-258
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcServerLogic.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/configurations/NodeConfiguration.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.