Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: cfb34c1 ec36f7c)
Merge "Database issues with mdbc docker env"
authorBrendan Tschaen <ctschaen@att.com>
Thu, 24 Jan 2019 16:27:32 +0000 (16:27 +0000)
committerGerrit Code Review <gerrit@onap.org>
Thu, 24 Jan 2019 16:27:32 +0000 (16:27 +0000)
commitfa078d24e835af497d3286c4525ae09a6de8f3d9
treec44bd04267e43271274f8b4122caa1619eb852fatree | snapshot
parentcfb34c1b4f6701555df3bf7b9bdbf8caace966bccommit | diff
parentec36f7c8662d3a90e78d6c59d8d45e11dbce16abcommit | diff
Merge "Database issues with mdbc docker env"
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.