Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: ad9faf2 e162ac7)
Merge "Docker compose scripts for two mdbc sites"
authorBharath Balasubramanian <bharathb@research.att.com>
Fri, 14 Dec 2018 05:51:31 +0000 (05:51 +0000)
committerGerrit Code Review <gerrit@onap.org>
Fri, 14 Dec 2018 05:51:31 +0000 (05:51 +0000)
commit63501e658066efaf4e58dff16245521a1072efaf
tree8402df8926294c8fe1f4eda0b1ce3a3633af3c19tree | snapshot
parentad9faf285c9348728859c49b0883bff82ec5031ecommit | diff
parente162ac7ac117d2a1948ec2ea6845d0e132b2967ecommit | diff
Merge "Docker compose scripts for two mdbc sites"
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.