Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: a1c1b4b a660644)
Merge "Remove benchmarks"
authorThomas Nelson <nelson24@att.com>
Thu, 4 Apr 2019 18:44:28 +0000 (18:44 +0000)
committerGerrit Code Review <gerrit@onap.org>
Thu, 4 Apr 2019 18:44:28 +0000 (18:44 +0000)
commit361533ff29d77c78a418967229e9fc6d72d46bd6
tree9c19f19846149a0ea76de4a026ebe5e402e7b15etree | snapshot
parenta1c1b4ba47e9c8ef1fa4e7b8a3ea8ab272050baecommit | diff
parenta660644ff0adf5d5d3aec430feeeb6d848a799e5commit | diff
Merge "Remove benchmarks"
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.