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.

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.

Grokmirror user

about summary refs log tree commit diff stats

diff options

author	Jessica Wagantall <jwagantall@linuxfoundation.org>	2018-05-10 17:19:34 +0000
committer	Gerrit Code Review <gerrit@onap.org>	2018-05-10 17:19:34 +0000
commit	fc12ebdd86470ad62036e6b0660179f90253f63f (patch)
tree	4b825dc642cb6eb9a060e54bf8d69288fbee4904

Initial empty repository

Diffstat

0 files changed, 0 insertions, 0 deletions


context:
space:
mode: