Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: 8a3db86 52159a5)
Merge "Implement postgres, fixes to eventual, and many bug fixes"
authorBrendan Tschaen <ctschaen@att.com>
Wed, 15 May 2019 15:08:05 +0000 (15:08 +0000)
committerGerrit Code Review <gerrit@onap.org>
Wed, 15 May 2019 15:08:05 +0000 (15:08 +0000)
commit96933528fdd51e606e48d79941ce43249ffb48b6
treeefec05eb72232c030e442eb12afa2260d6b6bd67tree | snapshot
parent8a3db86e697de59a29e712d23e771c8718f9778acommit | diff
parent52159a510dc31ee1dacf612a1e05cc8612a117e5commit | diff
Merge "Implement postgres, fixes to eventual, and many bug fixes"
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcConnection.java diff1 | diff2 | blob | history
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.