Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 2a4f867 c260a14)
Merge "Switch to using mariadb connector"
authorThomas Nelson <nelson24@att.com>
Thu, 31 Jan 2019 22:46:22 +0000 (22:46 +0000)
committerGerrit Code Review <gerrit@onap.org>
Thu, 31 Jan 2019 22:46:22 +0000 (22:46 +0000)
commitc20b9e36ef6a262a841231e972e6e3ecad0adc15
treea8dca11e1a251beaf62323f4ef8fb0e90a4e97c6tree | snapshot
parent2a4f867f4e6b8c896124958885119475eee1cbb0commit | diff
parentc260a14f888e09ce767ac6b9f6353c87f0cd034dcommit | diff
Merge "Switch to using mariadb connector"
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.