Read write lock implementation - 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-21 13:19:40 -0400
committer	Tschaen, Brendan <ctschaen@att.com>	2019-05-22 15:29:58 -0400
commit	92a80130ba924dc7b101b978bdad1d0fba14b141 (patch)
tree	5bee5c732a20600c82a497b1463641a69b135559 /version.properties
parent	ed4b4af2de4b02efd3f097323e9a999f905e60e6 (diff)

Read write lock implementation

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

Diffstat (limited to 'version.properties')

0 files changed, 0 insertions, 0 deletions