Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 618b632 654d7e7)
Merge "New multi-threaded test client script"
authorBrendan Tschaen <ctschaen@att.com>
Tue, 9 Jul 2019 18:26:10 +0000 (18:26 +0000)
committerGerrit Code Review <gerrit@onap.org>
Tue, 9 Jul 2019 18:26:10 +0000 (18:26 +0000)
commit757040c487343e81a4399bd7030e1ba881c2d141
tree70ee626d668bd56a323b248a62772c5b917e23cctree | snapshot
parent618b63253109a373909aa46452e16811302a24e7commit | diff
parent654d7e7cc76bf98ad29d93cfa53c37cafa79a1f0commit | diff
Merge "New multi-threaded test client script"
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.