MusicSqlManager Removal, othe code refactors - music/mdbc - 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.

diff options

author	Tschaen, Brendan <ctschaen@att.com>	2018-11-20 15:29:12 -0500
committer	Tschaen, Brendan <ctschaen@att.com>	2018-11-20 15:43:30 -0500
commit	1359f1023594c201b91fff73b2baa3f5d5cf6fd6 (patch)
tree	30c3ac2940f82414a76e59bc8ed916ab9599b5f2 /pom.xml
parent	83db3eb4ccf7e636f586a6873a966e14ba1685ae (diff)

MusicSqlManager Removal, othe code refactors

MusicSqlManager not required in current setup Current code condensed and absorbed into MdbcConnection and MusicMixin Modify deprecated names "CassandraMixin" to "MusicMixin" Change-Id: If68f8937a385c19d901c56e5795ddc0acf45d399 Issue-ID: MUSIC-198 Signed-off-by: Tschaen, Brendan <ctschaen@att.com>

Diffstat (limited to 'pom.xml')

0 files changed, 0 insertions, 0 deletions


context:
space:
mode: