Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: d4350cb) | patch
Remove netty dependency pulled in by music library 35/75035/1
authorTschaen, Brendan <ctschaen@att.com>
Thu, 20 Dec 2018 22:27:54 +0000 (17:27 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 20 Dec 2018 22:27:54 +0000 (17:27 -0500)
commitbde93d748fd26d3f0447a434b92009aa9f24ba7e
treeefb02aceafa66a6ef5e25dfd661457269b9a6a43tree | snapshot
parentd4350cbfa330afbb5c51e42e5c1572f6478c5905commit | diff
Remove netty dependency pulled in by music library

Issue-ID: MUSIC-265

Change-Id: I04a403653db4bb989901a565cf64f85a0ed2239b
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.