Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 05e7271 4bc956d)
Merge "Shutdown hook logic"
authorBharath Balasubramanian <bharathb@research.att.com>
Sun, 17 Mar 2019 21:50:44 +0000 (21:50 +0000)
committerGerrit Code Review <gerrit@onap.org>
Sun, 17 Mar 2019 21:50:44 +0000 (21:50 +0000)
commit6f363a89863a91ac104e5c77f0096636a8db5343
tree989c46579a97da33fceb17e16d8e9674c170720ctree | snapshot
parent05e72711ca4f45da24c445dec8669877ed31830ccommit | diff
parent4bc956de441cff664657a77a609081ce154e1759commit | diff
Merge "Shutdown hook logic"
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.