Relinquish locks for each transaction - 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>	2019-05-28 10:03:24 -0400
committer	Tschaen, Brendan <ctschaen@att.com>	2019-05-30 16:08:07 -0400
commit	e2031a7220812eec652354c3c705c81ef30b9dea (patch)
tree	f8f286b47657724e0a39e4b6ae4f8bb2d7b2b03f /mdbc-server/src/main/java/org/apache
parent	65b45cafb4dff93bef52e91f2ab3f2a772e4472e (diff)

Relinquish locks for each transaction

Change-Id: I44c10c0cc7857cfb647386507218a4e608b24687 Issue-ID: MUSIC-399 Signed-off-by: Tschaen, Brendan <ctschaen@att.com>

Diffstat (limited to 'mdbc-server/src/main/java/org/apache')

0 files changed, 0 insertions, 0 deletions