Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 95d22d7) | patch
Change MDBC version, nexus repo property 98/71898/1
authorArthur Martella <arthur.martella.1@att.com>
Mon, 5 Nov 2018 21:58:23 +0000 (16:58 -0500)
committerArthur Martella <arthur.martella.1@att.com>
Mon, 5 Nov 2018 21:58:23 +0000 (16:58 -0500)
commit71b2712a0c9d968c36ef59bcfad1b0add8e82592
treed2ff0e064c9b73d475eaa7a1546333afe3afdbabtree | snapshot
parent95d22d7491ea365fdc4525e44d484c73c33e16a1commit | diff
Change MDBC version, nexus repo property

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